From: Joel Brobecker <brobecker@adacore.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sources.redhat.com
Subject: Re: [MI] -exec-return or CLI 'return' do not trigger MI events
Date: Fri, 12 Feb 2010 10:54:00 -0000 [thread overview]
Message-ID: <20100212105433.GR2919@adacore.com> (raw)
In-Reply-To: <hl3ag6$g3t$1@ger.gmane.org>
> For all I can tell, the 'return' command does not actually resume the
> target. It just pops the stack.
I got caught by this tiny but important detail as well. But if you look
at the GDB User's manual, it's very explicit about it. Among many things,
it says:
The return command does not resume execution; it leaves the program
stopped in the state that would exist if the function had just returned.
In contrast, the finish command (see Continuing and Stepping) resumes
execution until the selected stack frame returns naturally.
--
Joel
next prev parent reply other threads:[~2010-02-12 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 19:50 Marc Khouzam
2010-02-12 10:29 ` Vladimir Prus
2010-02-12 10:54 ` Joel Brobecker [this message]
2010-02-12 15:33 ` Marc Khouzam
2010-02-12 15:37 ` Vladimir Prus
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=20100212105433.GR2919@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sources.redhat.com \
--cc=vladimir@codesourcery.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