Re: [GDB/MI] missing token in "stopped" output after -exec-run?

Vladimir Prus
2008-05-21T05:05:20Z

Joel Brobecker wrote:

....
>
*stopped,reason="breakpoint-hit",disp="del",bkptno="1",thread-id="1",frame={addr="0x08048332",func="main",args=[],file="foo.c",fullname="/home/no-backup/brobecke/head-merge/ex/foo.c",line="6"}
>
> A few weeks ago, the output looked like this:
>
> 232-exec-run
> 232^running
> (gdb)
> 232*stopped,reason="breakpoint-hit",disp="del",...
>
> The token was preserved. Is the new behavior intended?

Yes (and I've explicitly posted to the list about this change, quite some time before
actually changing things). The situation is:

1. In current gdb, the token actually provides no information (since only
on run command can be active at a time).
2. No frontend author stepped in to say they care.
3. In non-stop mode, keeping the token is almost impossible.
4. The implementation of printing of the token was a mess.

Does it cause any problems for you?

- Volodya