Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <409CFB5C.4010205@gnu.org> (raw)
In-Reply-To: <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




      parent reply	other threads:[~2004-05-08 15:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-08  4:03 Randolph Chung
2004-05-08  4:52 ` Daniel Jacobowitz
2004-05-08  4:55   ` Randolph Chung
2004-05-08 15:23   ` Andrew Cagney [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=409CFB5C.4010205@gnu.org \
    --to=cagney@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=randolph@tausq.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox