This is the mail archive of the
mailing list for the binutils project.
RE: linker relocation of debug information
- From: Jeff Baker <jbaker at qnx dot com>
- To: 'Ian Lance Taylor' <ian at wasabisystems dot com>, Daniel Jacobowitz <drow at mvista dot com>
- Cc: binutils at sources dot redhat dot com, Jeff Baker <jbaker at qnx dot com>
- Date: Wed, 28 Jan 2004 14:51:51 -0500
- Subject: RE: linker relocation of debug information
Let's say, just for the sake of argument, that a developer was locked into
using binutils 2.12.1 and gdb 5.2.1 for an upcoming release. Let's also say
that this developer is unable to step into shared object because the debug
sections aren't relocated. What would you suggest as a solution?
> Daniel Jacobowitz <firstname.lastname@example.org> writes:
> > On Tue, Jan 27, 2004 at 04:31:16PM -0500, Ian Lance Taylor wrote:
> > > Jeff Baker <email@example.com> writes:
> > >
> > > > Does anyone remember when this behaviour was changed in the
> > >
> > > Well, see this message I wrote a few years back for some more
> > > background information. Even at the time the situation was confused.
> > > http://sources.redhat.com/ml/binutils/1999-q2/msg00046.html
> > Well, in reference to that specific confusion - I believe that GCC no
> > longer generates debug information which includes the address of
> > external symbols.
> Actually, the confusion I meant was that different targets behaved in
> different ways.
> I don't personally care what happens with this.