This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [committed] Use frame memory for code reading

From: Andrew Cagney <cagney at gnu dot org>
To: Daniel Jacobowitz <drow at false dot org>
Cc: Randolph Chung <randolph at tausq dot org>, gdb-patches at sources dot redhat dot com
Date: Sat, 08 May 2004 11:23:08 -0400
Subject: Re: [committed] Use frame memory for code reading
References: <20040508040258.GO3965@tausq.org> <20040508045237.GB5860@nevyn.them.org>

On Fri, May 07, 2004 at 09:02:58PM -0700, Randolph Chung wrote:
Ignore breakpoints when doing code reading during unwind, as suggested
by Andrew. commited. thanks -randolph
2004-05-07 Randolph Chung <tausq@debian.org>

* hppa-tdep.c (skip_prologue_hard_way, hppa_frame_cache): Use read_memory_nobpt for code reading when doing frame unwinding. * hppa-linux-tdep.c (insns_match_pattern): Likewise.
I'm guessing he actually meant get_frame_memory?

Yes, ``frame*memory'' variants as used by tramp-frame.

These are future proof - the assumption is that a frame can find its inferior which can find its memory.

I'm really not sure why we have this many memory access functions.

forcing parameterisation with flush this out.

Andrew

References:
- [committed] Use frame memory for code reading
  - From: Randolph Chung
- Re: [committed] Use frame memory for code reading
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]