From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11538 invoked by alias); 9 Jul 2003 12:24:01 -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 11510 invoked from network); 9 Jul 2003 12:24:00 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sources.redhat.com with SMTP; 9 Jul 2003 12:24:00 -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 IAA25178; Wed, 9 Jul 2003 08:15:16 -0400 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id IAA21325; Wed, 9 Jul 2003 08:23:59 -0400 Message-ID: <064e01c34615$0b152ae0$0202040a@catdog> From: "Kris Warkentin" To: "Andrew Cagney" Cc: "Gdb@Sources.Redhat.Com" References: <062401c34590$97cd09b0$0202040a@catdog> <3F0B315E.7000702@redhat.com> Subject: Re: [rfc] Print solib events in mi-mode Date: Wed, 09 Jul 2003 12:24:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-SW-Source: 2003-07/txt/msg00090.txt.bz2 Actually, I had looked at those and some other related threads. I suggested to our Eclipse guys that it would probably be easy for them to just implement it in the IDE (since all the apps and libs are already projects under IDE control) using the stop-on-solib-event mechanism. They countered that there was no mi feedback on whether an stop was solib related, hence my patch. If there's no objection to the output this provides, I wouldn't mind applying it. MI-ification is generally a good thing right? Is there somewhere I should document this as well? cheers, Kris ----- Original Message ----- From: "Andrew Cagney" To: "Kris Warkentin" Cc: "Gdb@Sources.Redhat.Com" Sent: Tuesday, July 08, 2003 5:02 PM Subject: Re: [rfc] Print solib events in mi-mode > > What do you think of something like this? When stop-on-solib-events is set, > > this will print the reason as being a shared-lib-event. > > > > Our Eclipse team wants to be able to set breakpoints in shared libraries > > that aren't loaded yet. If they get notification of shlib-events, then they > > can re-examine the list of loaded libraries and set any breakpoints that > > have been enabled in the project's libs. > > See: [RFC] add 'save-breakpoints' command > http://sources.redhat.com/ml/gdb-patches/2001-12/threads.html#00114 > (but check for other related threads). > > The resolution was interesting, instead of adding a new command, modify > the existing command so that it would add breakpoints that would be > automatically enabled later. > > Andrew > > (although the patch is probably also useful) > > >