This is the mail archive of the
mailing list for the GDB project.
RE: [MI] -exec-return or CLI 'return' do not trigger MI events
> -----Original Message-----
> From: firstname.lastname@example.org
> [mailto:email@example.com] On Behalf Of Vladimir Prus
> Sent: Friday, February 12, 2010 5:28 AM
> To: firstname.lastname@example.org
> Subject: Re: [MI] -exec-return or CLI 'return' do not trigger
> MI events
> 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
> > (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.
Ok, but how does the frontend know the stack has been poped
and the editor should show a new line?
When we use GDB 7.0 we only listen for MI events to update the
I'll have to fix this for '-exec-return' anyway to support
GDB 7.0, but with respect to GDB itself, aren't we missing
some MI event then?