Re: breakpoints in shared libraries

[Bob Rossi <bob@brasko.net>]

On Tue, Feb 14, 2006 at 06:21:07PM +0100, Mark Kettenis wrote:
> > X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on 
> > 	elgar.sibelius.xs4all.nl
> > X-Spam-Level: 
> > X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=no 
> > 	version=3.1.0
> > X-From_: gdb-return-24270-m.m.kettenis=alumnus.utwente.nl@sourceware.org  Tue Feb 14 18:00:38 2006
> > Date: Tue, 14 Feb 2006 12:00:31 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: gdb@sourceware.org
> > Mail-Followup-To: Florian Hackenberger <f.hackenberger@chello.at>, 	gdb@sourceware.org
> > Content-Disposition: inline
> > X-IsSubscribed: yes
> > Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
> > Sender: gdb-owner@sourceware.org
> > X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information.
> > X-UTwente-MailScanner: Found to be clean
> > X-MailScanner-From: gdb-return-24270-m.m.kettenis=alumnus.utwente.nl@sourceware.org
> > 
> > On Tue, Feb 14, 2006 at 05:29:09PM +0100, Florian Hackenberger wrote:
> > > Pending breakpoint "quaternion.cpp:100" resolved
> > > Quaternion::Quaternion(angle, axis), axis is not unit.
> > > Make the axis unit.
> > > 
> > > That tells me:
> > > 1. The breakpoint was set.
> > > 2. The breakpoint did not work, as I can see the output "Make the axis unit." 
> > > and that's the line where my breakpoint was supposed to interrupt the 
> > > execution.
> > > 
> > > So that's the problem. Can anyone help me?
> > 
> > This has nothing to do with shared libraries; if you search the
> > archives for breakpoints in constructors, you'll learn lots more about
> > the (still unsolved) problem.
> 
> But Florian is setting a breakpoint using FILENAME:LINE syntax and not
> using FUNCTIONNAME syntax.  That should work isn't it?  At least as
> long as GCC is not inlining the constructor such that there are
> actually multiple copies in the code and GDB sets the breakpoint in a
> different copy than the one being executed.

I know this is probably obvious, but if you are desperate, you could
have your constructor call a new function that you write and then set a
breakpoint in the new function.

Bob Rossi