From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22033 invoked by alias); 7 May 2003 16:16:11 -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 22005 invoked from network); 7 May 2003 16:16:10 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 7 May 2003 16:16:10 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 49C502B2F; Wed, 7 May 2003 12:16:00 -0400 (EDT) Message-ID: <3EB93140.30803@redhat.com> Date: Wed, 07 May 2003 16:16:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alain Magloire Cc: gdb@sources.redhat.com Subject: Re: Event notification (was Re: GDB/MI lawyer for Thread Creation) References: <200305071519.LAA00443@node1.ott.qnx.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-05/txt/msg00090.txt.bz2 > 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. Hmm, makes sense - a real rationale. Anyone else have comments? Want to re-word the MI doco so this is clearer? > Questions: > Will kseitz_interps-20020528-branch be merge to the main trunk? > Any ETA ? The branch contains a lot of stuff, but importantly prototypes for two new features: - interps command - breakpoint events The interps feature is now implemented in the mainline. The breakpoint stuff has't been done. One missing bit of the framework needed for that feature - observer.[hc] - was recently added by Joel though. > I'm exited about this, it brings be closer in providing a more powerfull/flexible > gui debugger. Andrew