From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-29430-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 26911 invoked by alias); 24 Aug 2007 18:25:10 -0000
Received: (qmail 26771 invoked by uid 22791); 24 Aug 2007 18:25:08 -0000
X-Spam-Check-By: sourceware.org
Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 24 Aug 2007 18:25:00 +0000
Received: (qmail 8904 invoked from network); 24 Aug 2007 18:24:58 -0000
Received: from unknown (HELO localhost) (jimb@127.0.0.2)   by mail.codesourcery.com with ESMTPA; 24 Aug 2007 18:24:58 -0000
To: "Veenu Verma (AS/EAB)" <veenu.verma@ericsson.com>
Cc: "Daniel Jacobowitz" <drow@false.org>, 	  "Mark Kettenis" <mark.kettenis@xs4all.nl>,  <gdb@sourceware.org>
Subject: Re: Thread exit & create events
References: <9171BA436A79BF46953672FB5A11DA5E012B45C6@esealmw104.eemea.ericsson.se> 	<200708241046.l7OAkOel020079@brahms.sibelius.xs4all.nl> 	<20070824120037.GA1084@caradoc.them.org> 	<9171BA436A79BF46953672FB5A11DA5E012B4730@esealmw104.eemea.ericsson.se> 	<20070824121922.GA2374@caradoc.them.org> 	<9171BA436A79BF46953672FB5A11DA5E012B47B7@esealmw104.eemea.ericsson.se>
From: Jim Blandy <jimb@codesourcery.com>
Date: Fri, 24 Aug 2007 18:25:00 -0000
In-Reply-To: <9171BA436A79BF46953672FB5A11DA5E012B47B7@esealmw104.eemea.ericsson.se> (Veenu Verma's message of "Fri, 24 Aug 2007 15:14:53 +0200")
Message-ID: <m3fy28x01x.fsf@codesourcery.com>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2007-08/txt/msg00199.txt.bz2


"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.