Re: ldd strange behaviour
On Thu, 18 Dec 1997, Alex Romosan wrote:
> i have a c++ program compiled with no debug flag. when i do an ldd on
> the executable i get the following:
>
> ldd ./vat
> libtk8.0.so.1 => /usr/lib/libtk8.0.so.1 (0x4000f000)
> libtcl8.0.so.1 => /usr/lib/libtcl8.0.so.1 (0x400af000)
> libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40115000)
> libnsl.so.1 => /lib/libnsl.so.1 (0x401b8000)
> libdl.so.2 => /lib/libdl.so.2 (0x401be000)
> ---> libstdc++.so.2.7.2 => /usr/lib/libg++-dbg/libstdc++.so.2.7.2 (0x401c1000)
> libm.so.6 => /lib/libm.so.6 (0x401fe000)
> libc.so.6 => /lib/libc.so.6 (0x40218000)
>
> if i take /usr/lib/libg++-dbg out of /etc/ld.so.conf an rerun
> 'ldconfig -v' i get this:
>
> ldd ./vat
> libtk8.0.so.1 => /usr/lib/libtk8.0.so.1 (0x4000f000)
> libtcl8.0.so.1 => /usr/lib/libtcl8.0.so.1 (0x400af000)
> libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40115000)
> libnsl.so.1 => /lib/libnsl.so.1 (0x401b8000)
> libdl.so.2 => /lib/libdl.so.2 (0x401be000)
> ---> libstdc++.so.2.7.2 => /usr/lib/libstdc++.so.2.7.2 (0x401c1000)
> libm.so.6 => /lib/libm.so.6 (0x401fe000)
> libc.so.6 => /lib/libc.so.6 (0x40219000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>
> which, i think, should be the right dependency. is this a bug? which
> version of the c++ library is the program actually linked against? i
> have both libg++272-dbg and libg++272-dev installed (version
> 2.7.2.8-0.1 from hamm). ldd is from ldso-1.9.6-2. any clues?
Actually, the strange behavior is correct and expected (which is why
libg++-dbg does it). Libg++-dbg puts /usr/lib/libg++-dbg/ in ld.so.conf.
The debugging library isn't any slower, it just contains debugging symbols
for use by gdb. It is, otherwise, identical to the non debugging version
of the library.
--
Scott K. Ellis <storm@gate.net> http://www.gate.net/~storm/
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: