From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: wkf@sinavigator.com, gdb@sourceware.org
Subject: Re: Step outer function call
Date: Tue, 29 Jan 2008 04:19:00 -0000 [thread overview]
Message-ID: <ur6g1jmc8.fsf@gnu.org> (raw)
In-Reply-To: <20080128201939.GA12178@caradoc.them.org> (message from Daniel Jacobowitz on Mon, 28 Jan 2008 15:19:39 -0500)
> Date: Mon, 28 Jan 2008 15:19:39 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb@sourceware.org
>
> On Mon, Jan 28, 2008 at 12:12:52PM -0800, William K. Foster wrote:
> > Hi,
> >
> > I don't know much about the debug formats, but it seems to me that since
> > the debugger knows what line number it is on in the source code, it
> > should be able to locate the last function call on that line number and
> > enter it for this hypothetical command that many people seem to want.
> >
> > Am I missing something?
>
> Yes, generally we can't locate the last function call.
Can we locate all of them? If so, perhaps we could (optionally)
display a menu of them and ask the user where she wants to step.
next prev parent reply other threads:[~2008-01-29 4:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 19:55 William K. Foster
2008-01-28 20:03 ` Marc Khouzam
2008-01-28 20:10 ` Daniel Jacobowitz
2008-01-28 20:13 ` William K. Foster
2008-01-28 20:20 ` Daniel Jacobowitz
2008-01-29 4:19 ` Eli Zaretskii [this message]
2008-01-29 6:44 ` Michael Snyder
2008-01-28 22:36 ` Michael Snyder
2008-01-28 23:00 ` Nick Roberts
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=ur6g1jmc8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=wkf@sinavigator.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