From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb@sources.redhat.com
Subject: Re: [MI] -exec-return or CLI 'return' do not trigger MI events
Date: Fri, 12 Feb 2010 10:29:00 -0000 [thread overview]
Message-ID: <hl3ag6$g3t$1@ger.gmane.org> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC515FB3D4EE@EUSAACMS0703.eamcs.ericsson.se>
Marc Khouzam wrote:
> Hi,
>
> I just noticed that GDB 7.0.1 does not issue MI events
> *running and *stopped for the CLI 'return' command.
> This is the relevant output, while the whole (small)
> session is after.
>
> (gdb) -exec-return
>
^done,frame={level="0",addr="0x08048412",func="foo",args=[],file="a.cc",fullname="/local/lmckhou/testing/a.cc",line="6"}
> (gdb) return
> &"return\n"
> ~"#0 main () at a.cc:9\n"
> ~"9\t return 0;\n"
> ^done
>
> Do you want me to write a bug?
For all I can tell, the 'return' command does not actually resume the target.
It just pops the stack.
- Volodya
next prev parent reply other threads:[~2010-02-12 10:29 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 [this message]
2010-02-12 10:54 ` Joel Brobecker
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='hl3ag6$g3t$1@ger.gmane.org' \
--to=vladimir@codesourcery.com \
--cc=gdb@sources.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