From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: GDB Patches <gdb-patches@sources.redhat.com>,
Stan Shebs <shebs@apple.com>
Subject: Re: RFC: reverse-finish
Date: Wed, 28 Sep 2005 18:26:00 -0000 [thread overview]
Message-ID: <433AE066.5000301@redhat.com> (raw)
In-Reply-To: <20050926014832.GF22284@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Wed, Sep 21, 2005 at 11:17:51AM -0700, Michael Snyder wrote:
>
>>+ if (find_pc_partial_function (get_frame_pc (get_current_frame ()),
>>+ NULL, &func_addr, NULL) == 0)
>>+ internal_error (__FILE__, __LINE__,
>>+ "Finish: couldn't find function.");
>
>
> This shouldn't be an internal error; it's quite easy to provoke it from
> the command line, so it should be at worst an error(). And please use
> _() for the message eventually :-)
Sounds good.
>>+ sal = find_pc_line (func_addr, 0);
>
>
> I think it's not a good idea to use the line table for this. You want
> a breakpoint at, literally, the first instruction of the function. So
> just create one. Avoids problems with broken line information, et
> cetera.
Ah. You're right, I think I cut'n'pasted this from
step_into_function. In this context, we want to step
*out of* the function.
>>+ /* Tell the breakpoint to keep quiet. */
>>+ breakpoint_muzzle (breakpoint);
>
>
> Not sure what this patch is against, but we don't have
> breakpoint_muzzle :-)
Oh, sorry -- just a hack to keep the breakpoint
from being "mentioned". I'm sure there's a better
way of doing it.
prev parent reply other threads:[~2005-09-28 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 18:18 Michael Snyder
2005-09-26 1:48 ` Daniel Jacobowitz
2005-09-28 18:26 ` Michael Snyder [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=433AE066.5000301@redhat.com \
--to=msnyder@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=shebs@apple.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