Re: GDB/MI async output token field

[Bob Rossi <bob at brasko dot net>]

On Sun, May 25, 2014 at 11:16:05AM +0400, Vladimir Prus wrote:
> On 05/23/2014 05:14 AM, Bob Rossi wrote:
> >Hi,
> >
> >I'm slowly working through the GDB/MI output command functionality.
> >
> >On this page,
> >https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Output-Syntax.html#GDB_002fMI-Output-Syntax
> >
> >The documentation says,
> >  Note that for all async output, while the token is allowed by the
> >  grammar and may be output by future versions of gdb for select async
> >  output messages, it is generally omitted.
> >
> >  Frontends should treat all async output as reporting general changes in
> >  the state of the target and there should be no need to associate async
> >  output to any prior command.
> >
> >I searched through the GDB source code and can't find a single place
> >where this occurs.
> >
> >Does anyone know how to make a token appear in the async record?
> >Did older versions do it?
> >
> >If GDB is not using this feature, I propose we remove this information
> >from the manual until we actually need the functionality.
> 
> Bob,
> 
> such clarification will be good.

Hi,

I've got a patch to change the documentation to remove the tokens from
the async output records. I saw this in the ChangeLog,

2008-04-24  Vladimir Prus  <vladimir@codesourcery.com>

        * gdb.texinfo (GDB/MI Output Syntax): Clarify that async
         output does not necessary include any tokens.

That looked a little suspicous. That is, perhaps there are cases were
the token is in the async output?

Are you aware of any such cases? It doesn't look like the current
version of GDB emits this information, but perhaps older versions do?

Before I submit my patch I'd like to have this issue resolved.
It doesn't make sense to submit my current patch if old versions of GDB
can produce this content.

Thanks,
Bob Rossi