Visual History Report - Week 1,2

[David Faure]

On Tuesday 19 July 2005 20:30, Thiago Macieira wrote:
> David Faure wrote:
> >You can't set a breakpoint on a dynamically opened module before that
> > module is loaded. So you can't just "gdb konqueror ; break <whatever>".
> 
> With recent gdbs you can: it'll ask you if you want to create a breakpoint 
> for a module yet to be loaded.
> 
> Generally that's a bad idea because you'll very likely mistype the 
> function signature (namespace, arguments, constness, etc.)

Yeah that's why I don't even consider this an option ;-)
But for copy/paste from a previous gdb session it would work, indeed.

> >But if you start konqueror in gdb, run it, and once the sidebar is
> > there, use Ctrl-C to get control in gdb again, and then set a
> > breakpoint, then it should work. Subdirs are certainly no problem. I
> > assume you compiled kdebase with --enable-debug=full, this gives you
> > coherent behavior in gdb; otherwise with the optimization you see very
> > strange line jumping in gdb.
> 
> Also don't compile the code with optimisation (-O2 or -O1), or you'll see 
> the line-jumping David is talking about.

(In the KDE build system, --enable-debug=full removes optimisations)

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).