From: Andrew Cagney <cagney@gnu.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] frv-tdep.c: Use refine_prologue_limit() instead of skip_prologue_using_sal()
Date: Sat, 31 Jul 2004 17:38:00 -0000 [thread overview]
Message-ID: <410BD8F3.7060106@gnu.org> (raw)
In-Reply-To: <20040730152419.58cd727f@saguaro>
> + Note: kevinb/2004-07-29: Not true. On FR-V, I've encountered a
> + case where skip_prologue_using_sal() doesn't make it past the
> + first prologue -> body transition. */
The rs6000 contains this:
if (lim_pc == 0)
lim_pc = refine_prologue_limit (pc, lim_pc);
which I believe scores as a ``Not not true'' :-)
More seriously, what's the case you've encountered?
GDB should be using the dwarf2 debug info when setting the prologue
breakpoint[s], how hard is it to do that?
Andrew
PS: I'd keep the two comments separate, M-w or indent will merge them :-)
next prev parent reply other threads:[~2004-07-31 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 22:24 Kevin Buettner
2004-07-31 17:38 ` Andrew Cagney [this message]
2004-08-02 19:42 ` Kevin Buettner
2004-08-03 14:46 ` 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=410BD8F3.7060106@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.com \
/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