This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
RE: how to debug deman-loaded programs
- From: "Banibrata Dutta" <dutta at india dot hp dot com>
- To: <binutils at sources dot redhat dot com>
- Date: Wed, 28 Apr 2004 09:59:51 +0530
- Subject: RE: how to debug deman-loaded programs
sorry, one update, i forgot to compile 1 small section with -g.
on doing that i do not see the "rtld.c" anymore, but i see only
the source code corresponding to the innermost-level of static-
code (i.e. part of code that does dlopen(), not the part of any
shared object that is demand loaded).
> -----Original Message-----
> From: binutils-owner@sources.redhat.com
> [mailto:binutils-owner@sources.redhat.com] On Behalf Of
> Banibrata Dutta
> Sent: Wednesday, April 28, 2004 9:51 AM
> To: binutils@sources.redhat.com
> Subject: how to debug deman-loaded programs
>
>
> hi,
>
> how does one debug a demand-loaded part of a process, i.e.
> the fault is suspected in the shared object part of a
> program, which has been loaded on-demand using
> dlopen()/dlsym(), but when i run gdb on it (or it's "core"),
> going to a stack frame, and doing list, doesn't provide me
> with any info, but simply prints out "rtld.c", that's it. all
> my code is compiled with "-g" option.
>
> thanks & regards,
> Banibrata Dutta
> Hewlett-Packard ISO Pvt. Ltd,
> 29, Cunningham Road,
> Bangalore - 560052, India.
> Tel: +91-80-22051796
>
>