From: Justin Carlson <carlson@sibyte.com>
To: linux-mips@oss.sgi.com
Subject: GDB 5 for mips-linux/Shared library loading with new binutils/glibc
Date: Fri, 26 Jan 2001 17:40:07 -0800 [thread overview]
Message-ID: <0101261750492Y.00834@plugh.sibyte.com> (raw)
Working with some pretty bleeding edge GNU tools, here, and there doesn't seem
to be any support for mips-linux in GDB 5. Has anyone else run across this,
and, if so, are there patches available somewhere?
Also, I've run into a problem with ld.so from glibc-2.2 on mips32-linux. After
some hunting, I found that the templates in elf32bsmip.sh for gnu ld have
recently changed to support SHLIB_TEXT_START_ADDR as a (non-zero) base address
for shared library loading. SHLIB_TEXT_START_ADDR defaults to 0x5ffe0000 in
the current sources.
I'm curious if anyone knows the rationale for these changes. Best conjecture
I've heard is that it allows ld.so to not have to relocate itself, as it will
load by default to the high address.
However, ld.so seems to know nothing about relocating shared library with a
non-zero shared library base address, which causes dynamically linked stuff to
crash spectacularly.
I think fixing ld.so won't be too difficult, but I'm really wanting to find out
why these changes were made. And whether I'm reinventing some wheels by fixing
ld.so to cope with the new binutils stuff.
Anyone tread the ground before?
binutils we're using is from CVS as of about Dec 17th. Glibc is also a
snapshot from about the same time.
-Justin
next reply other threads:[~2001-01-27 1:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 1:40 Justin Carlson [this message]
2001-01-27 8:01 ` GDB 5 for mips-linux/Shared library loading with new binutils/glibc Maciej W. Rozycki
2001-01-27 19:01 ` Ralf Baechle
2001-01-28 11:55 ` Andreas Jaeger
2001-02-09 0:31 ` Kevin D. Kissell
2001-02-09 0:31 ` Kevin D. Kissell
2001-02-09 2:00 ` Ralf Baechle
2001-02-09 2:00 ` Ralf Baechle
2001-01-29 15:34 ` Maciej W. Rozycki
2001-01-27 19:11 ` Ralf Baechle
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=0101261750492Y.00834@plugh.sibyte.com \
--to=carlson@sibyte.com \
--cc=linux-mips@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.