This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: More info on static binary/libnss* mystery

On Sun, Oct 06, 2002 at 01:40:50AM -0700, Roland McGrath wrote:
> That doesn't really help us locate the problem itself.  What we need is
> more information about the crashes themselves.

Ok, I'm a little out of my depth here, so if you could tell me exactly
what you need, I'll do my best.

It would be much simpler if you could reproduce the problem. Basically,
any statically linked app crashes when it tries to resolve uids/gids.
For eg: "ls -l"

Here is a surefire way for me (and others) to reproduce:-

 * start with a glibc-2.2.5/gcc-3.2/binutils-2.13 based system
 * grab GNU fileutils-4.1, compile & link statically "make LDFLAGS=-static"
 * take the "ls" binary to a glibc-2.3 based system and execute "./ls -l"

I've just rebuilt glibc-2.3 with current gcc-3.2.1 cvs and
binutils- and the problem persists.

Unfortunately, my glibc-2.2.5 based system has the debug symbols stripped.
I compiled and installed a fresh 2.2.5 into a non-standard location then
linked fileutils against this "debug" glibc.

Interestingly, ls -l now runs without crashing. But it still doesn't resolve
the uids/gids.

Thanks for any help.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]