|Debugger Info firstname.lastname@example.org (shamanth) (2002-07-21)|
|Re: Debugger Info email@example.com (Paul Pluzhnikov) (2002-07-24)|
|Re: Debugger Info Mark.van.den.Brand@cwi.nl (M.G.J. van den Brand) (2002-07-25)|
|Re: Debugger Info firstname.lastname@example.org (Joachim Durchholz) (2002-07-25)|
|Re: Debugger Info email@example.com (Marco van de Voort) (2002-07-31)|
|Re: Debugger Info firstname.lastname@example.org (Momchil Velikov) (2002-07-31)|
|Re: Debugger Info email@example.com (Sander Vesik) (2002-07-31)|
|Re: Debugger Info firstname.lastname@example.org (Paul Pluzhnikov) (2002-08-04)|
|Re: Debugger Info email@example.com (srikanth) (2002-08-14)|
|From:||"Paul Pluzhnikov" <firstname.lastname@example.org>|
|Date:||4 Aug 2002 11:41:39 -0400|
|Organization:||EarthLink Inc. -- http://www.EarthLink.net|
|References:||02-07-085 02-07-093 02-07-144|
|Posted-Date:||04 Aug 2002 11:41:39 EDT|
"Sander Vesik" <email@example.com> writes:
> Paul Pluzhnikov <firstname.lastname@example.org> wrote:
> > Here are the features that gdb lacks, or misfeatures (it may
> > - unable to set break points in DSO until that DSO has been
> > loaded (makes debugging static constructors rather tricky)
> I think this is a (mis)feature of the dynamic linker (ld.so) rather
> than the debugger. To do this you would need direct support for it
> in the dynamic linker (at the very least) or being able to use a
> different, debug-enbled dynamic linker. At least on ELF platforms.
From Solaris "Debugging a Program With dbx"
In the section discussing debugging shared libraries and LD_PRELOAD:
Whenever you load a new program, dbx automatically executes the
program up to the point where rtld has completed construction
of the link map. dbx then reads the link map and stores the
base addresses. After that, the process is killed and you see
the prompt. These dbx tasks are conducted silently.
Of course this does not address libraries loaded with dlopen(), but at
least you can immediately set breakpoints in explicitly-linked shared
libraries, without having to:
break main ## sets BP1
## hit BP1
In order to understand recursion you must first understand recursion.
Return to the
Search the comp.compilers archives again.