From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9857 invoked by alias); 24 Jan 2012 18:25:23 -0000 Received: (qmail 9845 invoked by uid 22791); 24 Jan 2012 18:25:21 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from imr3.ericy.com (HELO imr3.ericy.com) (198.24.6.13) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 24 Jan 2012 18:25:07 +0000 Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q0OIOwI7015567 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 24 Jan 2012 12:24:58 -0600 Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.142]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Tue, 24 Jan 2012 13:24:57 -0500 From: Marc Khouzam To: "'Tom Tromey'" CC: "'Pedro Alves'" , "'gdb-patches@sourceware.org'" Date: Tue, 24 Jan 2012 18:32:00 -0000 Subject: RE: [4/4] RFC: implement catch load and catch unload Message-ID: References: <4F19B998.2030308@redhat.com> In-Reply-To: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-01/txt/msg00835.txt.bz2 > -----Original Message----- > From: Tom Tromey [mailto:tromey@redhat.com]=20 > Sent: Tuesday, January 24, 2012 12:36 PM > To: Marc Khouzam > Cc: 'Pedro Alves'; 'gdb-patches@sourceware.org' > Subject: Re: [4/4] RFC: implement catch load and catch unload >=20 > >>>>> "Marc" =3D=3D Marc Khouzam writes: >=20 > Marc> Not having this command won't prevent CDI from debugging, > Marc> but will have two impacts, as far as I know: > Marc> 1- no more user feature to stop on lib events > Marc> 2- breakpoints set on non-loaded libs will no longer be > Marc> installed (since CDI does not use pending breakpoints, but > Marc> tries to plant failed bps at each new lib load event) >=20 > Just to be clear -- the command still exists and works. > What changed is how gdb reports it. It used to be that you would get: >=20 > -exec-continue > ~"Stopped due to shared library event." > *stopped >=20 > Now you will get: >=20 > -exec-continue > *stopped,reason=3D"solib-event",[more stuff] >=20 > I can even restore the old output if you really need it; though I'd > prefer we just keep on with a more purely MI solution. Funny. I found the following comment in our code: // GDB does not have reason when stopping on shared, hopefully // this will be fix in newer version meanwhile, we will use a hack // to cope. On most platform we can detect this state by looking at the // console stream for the phrase: // ~"Stopped due to shared library event\n" The good news is we do look for the 'reason' field first. Surprisingly we look for "shlib-event", but it is a one-line fix to use "solib-event" instead. Is the change already in HEAD? I can test with that just to be sure I haven't missed something. Thanks Marc