Relocs against unalloced sections in shared libraries
Fri Jan 10 14:24:00 GMT 2003
Daniel Jacobowitz <firstname.lastname@example.org> writes:
|> On Thu, Jan 09, 2003 at 04:39:08PM -0800, Geoff Keating wrote:
|> > > From: Andreas Schwab <email@example.com>
|> > > Date: 10 Jan 2003 01:29:50 +0100
|> > > Geoff Keating <firstname.lastname@example.org> writes:
|> > >
|> > > > Isn't this necessary for proper handling of DWARF2 debug information?
|> > >
|> > > The debugger will know which bytes to relocate by looking at the
|> > > structure while reading the debug information from a shared library.
|> > Hmmm. Have you asked the GDB people about this? I believe the
|> > conclusion was that it kind-of does this now, and it kind-of works,
|> > but in the long run it should be looking at the relocations.
|> Yes. I don't know if it's possible to reproduce the situation in a
|> shared library on PPC (I haven't tried) but there are ET_REL objects
|> on PPC that _can not_ be debugged without properly obeying the
|> relocation information. That's because there can be relocations
|> against variables instead of against section symbols.
We are talking about ET_DYN objects, where this is a non-issue. Of
course, ET_REL object continue to contain the full relocation information.
Andreas Schwab, SuSE Labs, email@example.com
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 NÃ¼rnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
More information about the Binutils