Re: gdb + dynamic libs problem

[Daniel Jacobowitz <drow at mvista dot com>]

On Thu, Feb 20, 2003 at 01:26:13PM +0300, Lev Assinovsky wrote:
> > -----Original Message-----
> > From: Kevin Buettner [mailto:kevinb at redhat dot com]
> > Sent: Thursday, February 20, 2003 12:42 AM
> > To: Lev Assinovsky; gdb at sources dot redhat dot com
> > Subject: Re: gdb + dynamic libs problem
> > 
> > 
> > On Feb 18,  2:08pm, Lev Assinovsky wrote:
> > 
> > > I try to debug the application where dynamic objects 
> > > are loaded through user's dlopen explicit call.
> > > The only way to set breakpoint in .so is to open source after 
> > > .so got loaded (I have to detect this moment myself).
> > 
> > GDB can help you with this if you you do ``set 
> > stop-on-solib-events 1''.
> > You'll probably want to do this well after your program has started
> > though to avoid stopping every time one of the shared 
> > libraries specified
> > on the link line gets loaded.
> > 
> > > I perform source opening by issue the commands "shared library" and
> > > "list <file>:1".
> > 
> > Have you disabled ``auto-solib-add''?  If not, you shouldn't need to
> > invoke the ``sharedlibrary'' command directly.  I.e, gdb should
> > automatically load the shared libraries for you (unless you've told it
> > not to).
> 
> Here the point is! I don't have "classic" shared libraries like 
> libxxx.so. And application is not linked with them.
> I have xxx.so and load it via dlopen function. I.e. gdb doesn't have
> any knowledge about c++ files in my shared object until I type in "sharedlibrary" command!

GDB should still automatically load symbols for them.  You shouldn't
need to use "sharedlibrary".


-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer