From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9496 invoked by alias); 7 May 2003 15:19:49 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 9489 invoked from network); 7 May 2003 15:19:49 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sources.redhat.com with SMTP; 7 May 2003 15:19:49 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3p2/8.9.3) with ESMTP id LAA01240 for ; Wed, 7 May 2003 11:17:01 -0400 Received: from node1.ott.qnx.com (hwlab1 [10.0.2.159]) by smtp.ott.qnx.com (8.8.8/8.6.12) with ESMTP id LAA25289 for ; Wed, 7 May 2003 11:19:48 -0400 Received: (from alain@localhost) by node1.ott.qnx.com (8.8.8/8.6.12) id LAA00443 for gdb@sources.redhat.com; Wed, 7 May 2003 11:19:47 -0400 Message-Id: <200305071519.LAA00443@node1.ott.qnx.com> Subject: Event notification (was Re: GDB/MI lawyer for Thread Creation) To: gdb@sources.redhat.com Date: Wed, 07 May 2003 15:19:00 -0000 From: "Alain Magloire" In-Reply-To: <3EB82E49.2010207@redhat.com> from "Andrew Cagney" at May 06, 2003 05:51:05 PM MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2003-05/txt/msg00088.txt.bz2 > > > Bonjour > > > > Need a MI protocol guru for this. When threads are created gdb is sending > > > > gdb -i mi > > ~"[NEW Thread 1024 (LWP 8288)]\n" > > > > > > Useless for MI, how about a new OOB ? > > > > *thread,thread-id="8288" > > > > > > or a new async-notify ? > > > > =thread,thread-id="8288" > > > > Only "*stopped" is currently define as a possible oob. > > BTW, co/build kseitz_interps-20020528-branch, it also generates > breakpoint notify events. > > I think that notify is correct (although it could be argued that exec is > a legetimate class (the difference is a bit arbitrary). > I went digging in the old email exchanges with kseitz .... And yes this is what I'm looking for one nitpicking: - the event notifications mechanism seem to be for side effects, for example setting a breakpoint via CLI, notification is sent informing of the side effect. Or assigning statements having side effects. It does not seem to address "pure" async event. Threads creation/destruction, and loading of shared libs are two examples that spring to mind about the need of notification when the inferior is still running. It those cases, I would say that sending an OOB instead of async-notify is more appropriate. Questions: Will kseitz_interps-20020528-branch be merge to the main trunk? Any ETA ? I'm exited about this, it brings be closer in providing a more powerfull/flexible gui debugger.