RE: [RFA] fix *stopped for CLI commands

Marc Khouzam
2009-02-10T20:50:17Z

> Vladimir Prus
> Sent: Friday, February 06, 2009 2:45 AM
> To: gdb-patches@sources.redhat.com; Nick Roberts; Marc Khouzam
> Subject: [RFA] fix *stopped for CLI commands
>
> This patch fixes this by making MI observer print frame
> again, into MI uiout,
> if necessary.

I've applied the patch and tried it out. It works as expected
but it 'allowed' me to run into another problem.

When issuing a CLI command that triggers a ^running event,
the token id is not part of the ^running event anymore.
You can see this in the summarized session below.

26-exec-run
[...]
26^running <-- token is there for MI command
*running,thread-id="all"
(gdb)
[...]
(gdb)
27run
&"run\n"
[...]
^running <-- token is not there for CLI command
*running,thread-id="all"
(gdb)

I never noticed this before because DSF-GDB never uses CLI commands
that would trigger a ^running. So, to DSF-GDB it looks like the
CLI command never completed.

Thanks

Marc