From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25262 invoked by alias); 29 Jan 2004 18:38:52 -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 25117 invoked from network); 29 Jan 2004 18:38:49 -0000 Received: from unknown (HELO amsfep19-int.chello.nl) (213.46.243.20) by sources.redhat.com with SMTP; 29 Jan 2004 18:38:49 -0000 Received: from cable-62-205-65-11.upc.chello.be ([62.205.65.11]) by amsfep19-int.chello.nl (InterMail vM.6.00.05.02 201-2115-109-103-20031105) with ESMTP id <20040129183848.MGRJ1965.amsfep19-int.chello.nl@cable-62-205-65-11.upc.chello.be>; Thu, 29 Jan 2004 19:38:48 +0100 From: wim delvaux Organization: adaptive planet To: Daniel Jacobowitz Subject: Re: after 2 years of waiting for better ... Date: Thu, 29 Jan 2004 18:38:00 -0000 User-Agent: KMail/1.5.4 Cc: gdb@sources.redhat.com References: <200401271824.10298.wim.delvaux@adaptiveplanet.com> <20040127173334.GA18324@nevyn.them.org> In-Reply-To: <20040127173334.GA18324@nevyn.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401291938.47857.wim.delvaux@adaptiveplanet.com> X-SW-Source: 2004-01/txt/msg00333.txt.bz2 On Tuesday 27 January 2004 18:33, Daniel Jacobowitz wrote: > On Tue, Jan 27, 2004 at 06:24:10PM +0100, wim delvaux wrote: > > gdb is STILL not able to REMEMBER breakpoints in shared libraries that > > have been loaded with dlopen. > > > > VERY annoying !!!! When is somebody going to do something about this ? > > > > Situation example : > > > > b main > > step into function that is in a dlopened library. > > Set breakpoint in some statement of that function > > restart the application .... breakpoint is NOT met and application runs > > till exist ;-(((( > > > > HELP PLSE !! > > Two years later, GDB is still a volunteer project. I concur with that but i remember that some late 4.x version had a nice fix for that problem but somewhere in the mist of 5.x e.a. that fix got lost ;-( Where can I find that pending breakpoint work ? Thanx > > That said, I think Jeff's current work on pending breakpoints could be > used to fix this problem.