From: "H . J . Lu" <hjl@lucon.org>
To: Mark Kettenis <kettenis@wins.uva.nl>
Cc: nickc@cygnus.com, binutils@sourceware.cygnus.com
Subject: Re: Bug in dynamic linker
Date: Thu, 20 Jul 2000 11:04:00 -0000 [thread overview]
Message-ID: <20000720110416.A6252@lucon.org> (raw)
In-Reply-To: <200007201756.e6KHu8h18520@delius.kettenis.local>
On Thu, Jul 20, 2000 at 07:56:08PM +0200, Mark Kettenis wrote:
>
> Here it is (thanks for including the shar target :-)). By the way,
Sure.
> looks like there's something wrong with the linker. I get the
Yes, I fixed it and checked my fix into CVS :-). BTW, that is the
one we are discussing now.
> following output (with glibc 2.1.3):
>
> delius:~/tmp/needed$ make
> for f in threadtest test; do echo "Running: $f"; ./$f; \
> if [ $? != 0 ]; then echo Failed; fi; done
> Running: threadtest
> BUG IN DYNAMIC LINKER ld.so: dynamic-link.h: 57: elf_get_dynamic_info: Assertion `! "bad dynamic tag"' failed!
> Failed
> Running: test
> ./test: error in loading shared libraries: libthreadlib.so: cannot open shared object file: No such file or directory
> Failed
> for f in threadtest test; do echo "Running: ldd $f"; ldd ./$f; \
> if [ $? != 0 ]; then echo Failed; fi; done
> Running: ldd threadtest
> BUG IN DYNAMIC LINKER ld.so: dynamic-link.h: 57: elf_get_dynamic_info: Assertion `! "bad dynamic tag"' failed!
> ldd: /lib/ld-linux.so.2 exited with unknown exit code (127)
> Failed
> Running: ldd test
> libthreadlib.so => not found
> libc.so.6 => /lib/libc.so.6 (0x40015000)
> libpthread.so.0 => /lib/libpthread.so.0 (0x400f8000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
> delius:~/tmp/needed$ make
>
With the current linker from CVS,
# make
....
Running: ldd threadtest
libthreadlib.so => ./libthreadlib.so (0x40019000)
libc.so.6 => /lib/libc.so.6 (0x4002a000)
libpthread.so.0 => /lib/libpthread.so.0 (0x4013e000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
Running: ldd test
libthreadlib.so => not found
libc.so.6 => /lib/libc.so.6 (0x40028000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
If you think there still is a problem, please send me a testcase
to show it.
Thanks.
H.J.
next prev parent reply other threads:[~2000-07-20 11:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-20 6:06 Mark Kettenis
2000-07-20 9:04 ` H . J . Lu
2000-07-20 10:11 ` Mark Kettenis
2000-07-20 10:16 ` H . J . Lu
2000-07-20 10:56 ` Mark Kettenis
2000-07-20 11:04 ` H . J . Lu [this message]
2000-07-20 15:23 ` H . J . Lu
2000-07-20 9:23 ` Ulrich Drepper
2000-07-20 9:51 ` H . J . Lu
2000-07-20 9:56 ` Ulrich Drepper
2000-07-20 10:02 ` H . J . Lu
-- strict thread matches above, loose matches on Subject: below --
2000-07-27 16:56 Nick Clifton
2000-07-27 17:49 ` H . J . Lu
2000-07-19 17:52 Nick Clifton
[not found] <Pine.GS4.4.10.10007171002550.7771-100000@express.larc.nasa.gov>
2000-07-17 7:12 ` Peter A Barros
2000-07-18 15:24 ` H . J . Lu
[not found] <963602772.24226.ezmlm@sources.redhat.com>
2000-07-14 13:35 ` bug " Peter A Barros
2000-07-14 23:27 ` Alan Modra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000720110416.A6252@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sourceware.cygnus.com \
--cc=kettenis@wins.uva.nl \
--cc=nickc@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).