From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: Randolph Chung <randolph@tausq.org>, gdb-patches@sources.redhat.com
Subject: Re: [committed] Use frame memory for code reading
Date: Sat, 08 May 2004 15:23:00 -0000
Message-id: <409CFB5C.4010205@gnu.org>
References: <20040508040258.GO3965@tausq.org> <20040508045237.GB5860@nevyn.them.org>
X-SW-Source: 2004-05/msg00242.html

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