From: Daniel Jacobowitz <drow@false.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [committed] Use frame memory for code reading
Date: Sat, 08 May 2004 04:52:00 -0000 [thread overview]
Message-ID: <20040508045237.GB5860@nevyn.them.org> (raw)
In-Reply-To: <20040508040258.GO3965@tausq.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?
I'm really not sure why we have this many memory access functions.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-05-08 4:52 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 [this message]
2004-05-08 4:55 ` Randolph Chung
2004-05-08 15:23 ` Andrew Cagney
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=20040508045237.GB5860@nevyn.them.org \
--to=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