Re: gdb + dynamic libs problem

[Kevin Buettner <kevinb at redhat dot com>]

On Feb 20,  1:26pm, Lev Assinovsky wrote:

> > > 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!

What does ``info shared'' show you prior to using the ``sharedlibrary''
command?

GDB *should* be loading your dlopen'd libraries automatically too.

> > > But if the source file is big gdb get crash.

Do you know why gdb is crashing?

> > > It there any way to increase gdb resources to consume 
> > > larger files (symbol tables?)
> > 
> > Which platform are you running on?  On most platforms, gdb should
> > be able to use whatever resources the operating system is able to
> > give it.  Thus, you may need to play around with ulimit, adjusting
> > the amount of memory, swap space, etc.
> 
> I tried solaris8-intel and solaris8-sparc platforms with ulimit=unlimited.

Are you running out of memory?  Do you have enough swap space?

Kevin