[Top] [All Lists]

Re: GDB 5 for mips-linux/Shared library loading with new binutils/glibc

To: Justin Carlson <>
Subject: Re: GDB 5 for mips-linux/Shared library loading with new binutils/glibc
From: "Maciej W. Rozycki" <>
Date: Sat, 27 Jan 2001 09:01:47 +0100 (MET)
In-reply-to: <>
Organization: Technical University of Gdansk
On Fri, 26 Jan 2001, Justin Carlson wrote:

> 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?

 Get gdb 5.0 from my site, at ''.

 I've contributed all patches I've written myself.  Unfortunately, most of
the code needed for gdb 5.0 to run on MIPS was taken from the 4.x CVS at  As such it is required all authors of patches have to have
their copyright assigned to FSF before committing them to the gdb CVS.

 I've asked people to resolve ownership of the code here some time ago,
but it seems nobody is really interested in getting this code into
official gdb, sigh... 

> Also, I've run into a problem with from glibc-2.2 on mips32-linux.  
> After
> some hunting, I found that the templates in 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.

 It's not that recent, actually.  What's the problem with this?  I can't
see any on mipsel-linux here.

> I'm curious if anyone knows the rationale for these changes.  Best conjecture
> I've heard is that it allows to not have to relocate itself, as it will
> load by default to the high address.  

 Not sure about this -- there are comments on it in glibc in

> However, seems to know nothing about relocating shared library with a
> non-zero shared library base address, which causes dynamically linked stuff to
> crash spectacularly.  

 Does it?  Please provide more details.  All of my system (linux 2.4.0,
glibc 2.2.1) is dynamically linked and it works fine.

> binutils we're using is from CVS as of about Dec 17th.  Glibc is also a
> snapshot from about the same time.

 Glibc should be fine as is although you might consider getting the 2.2.1
release.  You may try to check if patches from my binutils package (also
available at the mentioned site) solve certain or all of your problems. 
The patches have been proposed for an inclusion in the upcoming binutils
2.11 release -- I hope they will finally get there.


+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+        e-mail:, PGP key available        +

<Prev in Thread] Current Thread [Next in Thread>