On 17-02-05 20:47 -0600, Hareesh Nagarajan wrote:
> Hi,
>
> What are the libraries/programs that need to be compiled with '+debug'
> so that GDB has *all* the info to step through library functions? At
> present GDB does not seem to have STL info.
>
> Must I re-compile/re-emerge
> 1. glibc
> 2. libstdc++-v3
> ...?
>
> Thanks,
>
> Hareesh
>
> --
> [email protected] mailing list
>
Run ldd on the program you want to debug to know what it
links against.
Sample output from ldd `which vim`:
linux-gate.so.1 => (0xffffe000)
libncursesw.so.5 => /lib/libncursesw.so.5 (0xb7f9b000)
libgpm.so.1 => /usr/lib/libgpm.so.1 (0xb7f94000)
libperl.so.1 => /usr/lib/libperl.so.1 (0xb7e57000)
libutil.so.1 => /lib/libutil.so.1 (0xb7e53000)
libc.so.6 => /lib/libc.so.6 (0xb7d39000)
libm.so.6 => /lib/libm.so.6 (0xb7d16000)
libdl.so.2 => /lib/libdl.so.2 (0xb7d12000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb7cfe000)
libnsl.so.1 => /lib/libnsl.so.1 (0xb7ce9000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7cbb000)
/lib/ld-linux.so.2 (0x4a092000)
Which means glibc, ncurses, libperl, gpm and whatever libnsl
and libcrypt belong to :)
Time to being out equery...
I see, libcrypt is glibc and libnsl is also glibc!
--
[email protected] mailing list
