Subject: Re: ldd coredump
To: Szabolcs Szigeti <>
From: Bob Kemp <>
List: current-users
Date: 04/25/1994 21:57:18
> 	ldd /usr/libexec/ generates a with signal 11.
> 	Why is that? Why is the core from, not ldd?

Its because of the method that ldd uses to print the library listing.
If the file looks like an executable, ldd sets an environment var
LD_TRACE_LOADED_OBJECTS and fork/execs the file.  The dynamic loader checks for this var and if found just prints out the info
(which it has to hand).  The bug was in ldd not distinguishing
properly between a dynamic library (try "file") and a dynamic
executable in ldd.

and dynamic executables will just print out the info until
you unsetenv it.

I reported it a while ago, so it should be fixed in recent -currents.