Re: MI *stopped event with CLI commands

[Vladimir Prus <vladimir@codesourcery.com>]

Nick Roberts wrote:

>  > with the latest MI changes, when running in MI mode, a *stopped event is issued whenever
>  > the inferior stops, even if the last command was a CLI command.
>  > However, the stopped event is bare if the command is a CLI command.
>  > 
>  > *stopped
>  > instead of
>  > *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",thread-id="1",
>  >
stopped-threads="all",frame={addr="0x08048415",func="main",args=[],file="c.cc",fullname="c.cc",line="5"}
>  > 
>  > Was this intended?  And if so, what should a frontend do in this case?
>  > We can parse the CLI output or send MI commands to get the info...
>  > However, it seems to me that having to do that, defeats the purpose of having
>  > the *stopped event after CLI commands.
>  > 
>  > Wouldn't be nice if the stopped event always had the full information?
> 
> If you do:
> 
> set target-async on
> 
> first, you do get the full information.  Perhaps this should be the default
> for targets which can run asynchronously.

Probably. Though it does not change the fact that *stopped without details sounds
like a bug. I'll take a look, though it might take a few days.

- Volodya