Hi,
On Mon, 3 Jun 2002 17:23:48 -0400
Brett Viren <bv@bnl.gov> wrote
concerning "Re: [ROOT] debugging ROOT with gdb":
> > gdb seems not to be aware of it. Would I need to recompile the ROOT
> > libraries for gdb to be able to find it?
>
> Yes, very much so. Set environment variable ROOTBUILD=debug do a
> "make clean ; make".
Or, pass the option `--build=debug' to `configure' :-)
> Other things that may help:>
>
> - run and attach GDB to root.exe, not the usual "root" executable
> (some fancy fork/exec goes on in "root" to quickly parse cmd. line
> args and give the illusion of fast startup).
Is that's what it's for?
> - run GDB 5.x for better C++ support. v4 is pretty bad with C++.
Ah, someone is running Debian GNU/Linux testing at least :-)
> - set a break in main(), hit it, set the break you really want and
> then "continue". This gets around spurious "can not do i/o"
> (message paraphrased) GDB error.
Erh, I think that's a very kind paraphrase of that error message.
However, it does make sense - obviously you can not set a breakpoint
on a symbol before that symbol is defined, and it may not be defined
until you `dlopen' it.
> It would be nice to collect all these things in the root manual
> (maybe they are there, I haven't looked recently).
Well, one could also look in the GDB manual :-)
One last thing: Don't forget about gObjectTable - it's a very useful
thing for hunting down memory leaks and the like.
Yours,
____ | Christian Holm Christensen
|_| | -------------------------------------------------------------
| | Address: Sankt Hansgade 23, 1. th. Phone: (+45) 35 35 96 91
_| DK-2200 Copenhagen N Cell: (+45) 24 61 85 91
_| Denmark Office: (+45) 353 25 305
____| Email: cholm@nbi.dk Web: www.nbi.dk/~cholm
| |
This archive was generated by hypermail 2b29 : Sat Jan 04 2003 - 23:50:54 MET