From: Ryan Bradetich <rbradetich@uswest.net>
To: Matthew Wilcox <willy@debian.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] /lib/ld.so.1 (glibc) issues on 2.5 kernel??
Date: 18 Mar 2003 00:20:54 -0700 [thread overview]
Message-ID: <1047972053.19011.14.camel@beavis.ybsoft.com> (raw)
In-Reply-To: <1047919859.14507.21.camel@beavis.ybsoft.com>
I have spend some more time tracking this problem down.
I have found the offending line in the kernel that causes
this problem, the rest of the RGH_FIX can be eliminated.
The symptom is with this line:
NEW_AUX_ENT(AT_ENTRY, exec->e_entry);
in fs/binfmt_elf.c:create_elf_tables().
If the that line is executed when the
interpreter_type == INTERPRETER_NONE, the error shows up when
/lib/ld.so.1 is executed. This line is fine when when the
interpreter_type == INTERPRTER_ELF ... which explains why
the system runs normally, and the error only manifests itself
when /lib/ld.so.1 is executed by hand. (the /lib/ld.so.1 library
does not set a PT_INTERP, so the interpreter is not set, where as
if a binary is executed, the interpreter is set to ELF).
The assert caused by /lib/ld.so.1 is caused by this line
in rtld.c:
assert (GL(dl_rtld_map).l_libname); /* How else did we get here? */
This assert is in the else clause of this if statement:
if (! GL(dl_rtld_map).l_libname && GL(dl_rtld_map).l_name)
The whole purpose of this if statment, according to the comments,
is to deal with this senario, where the library was invoked directly,
and the PT_INTERP was not set.
I am rebuilding glibc from source on my C200 now (i.e. this will
probably take a while :)) and I will continue debugging. I just wanted
to give a status update in case someone else has an idea, or was working
on it.
Thanks,
- Ryan
--
Ryan Bradetich <rbradetich@uswest.net>
next prev parent reply other threads:[~2003-03-18 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 16:19 [parisc-linux] /lib/ld.so.1 (glibc) issues on 2.5 kernel?? Ryan Bradetich
2003-03-17 16:32 ` Matthew Wilcox
2003-03-17 16:50 ` Ryan Bradetich
2003-03-18 7:20 ` Ryan Bradetich [this message]
2003-03-20 8:15 ` Ryan Bradetich
2003-03-20 14:14 ` Carlos O'Donell
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=1047972053.19011.14.camel@beavis.ybsoft.com \
--to=rbradetich@uswest.net \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=willy@debian.org \
/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