Re: Thread exit & create events

[Jim Blandy <jimb@codesourcery.com>]

"Veenu Verma (AS/EAB)" <veenu.verma@ericsson.com> writes:
>> No, but how are you getting these events in the first place?  Are you
> really parsing the ~"" console output?
>
>> I think you can find discussions of a real MI event for this sort of
> thing in the archives somewhere.
>
> Yes, we are parsing console output. 
> What do you mean by a real MI event ? Searched archive for "MI events"
> but didnt find anything related.

If you look at the grammar for GDB/MI in the GDB manual (under "GDB/MI
Output Syntax"), the MI protocol allows for asynchronous notification
output, which is marked by a '=':

`NOTIFY-ASYNC-OUTPUT ==>'
     `[ TOKEN ] "=" ASYNC-OUTPUT'

...

   * NOTIFY-ASYNC-OUTPUT contains supplementary information that the
     client should handle (e.g., a new breakpoint information).  All
     notify output is prefixed by `='.

What you should do is define a new ASYNC-CLASS, which is sent with
RESULTs that carry the thread identifiers you're interested in.