Re: execturing libc
Andreas Rottmann <firstname.lastname@example.org> writes:
> Adrian von Bidder <email@example.com> writes:
>> On Wednesday 02 February 2005 06.35, Brian M. Carlson wrote:
>>> I think you meant to ask, "Why would anyone want to execute the C
>>> bmc@blackhole:~$ /lib/ld-linux.so.2 /lib/libc.so.6
>> Ok, this is off topic for this thread, but still, strangely:
>> avbidder@humphrey:~$ /lib/ld-2.3.2.so /lib/libc-2.3.2.so
>> Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev->l_next == _rtld_local._dl_rtld_map.l_next' failed!
>> (sarge/i386) on self-made 2.6.10 (Debian kernel source
>> The system works fine, no random failures or anything.
> Same here (sarge/i386), kernel-image-2.6.8-2-k7
That error is the reason why libc is no longer executable. It used to
be. The error seems to come and go on some archs it seem, amd64 is
currently working fine:
mrvn@frosties:~% /lib64/ld-linux-x86-64.so.2 /lib/libc-2.3.2.so
GNU C Library stable release version 2.3.2, by Roland McGrath et al.
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
Compiled by GNU CC version 3.3.5 (Debian 1:3.3.5-6).
Compiled on a Linux 2.6.0-test7 system on 2005-01-12.
GNU libio by Per Bothner
crypt add-on version 2.1 by Michael Glad and others
NPTL 0.60 by Ulrich Drepper
NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Thread-local storage support included.
Report bugs using the `glibcbug' script to <firstname.lastname@example.org>.
And exactly that info is the reason why one may want to execute libc.