This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Spurious R_386_NONE relocations
- From: Jeff Baker <jbaker at qnx dot com>
- To: binutils at sources dot redhat dot com
- Date: Thu, 19 Aug 2004 14:14:04 -0400
- Subject: Spurious R_386_NONE relocations
- Organization: QNX Software Systems Ltd.
- Reply-to: jbaker at qnx dot com
I have a test project that, when compiled with gcc 2.95.3 and the latest
binutils, ends up with a load of R_386_NONE relocations. I've tried
tweaking our loader to ignore them, but the program crashes if you do
this so I'm under the impression that they are the result of bug. They
appear exclusively in the exception handling sections of a c++ shared
object.
I know that's pretty vague but does this sound familiar to anyone? The
problem doesn't exist with gcc 3.3.1+ but it looks like it's because the
compiler is outputting different code, not because the 'bug' has been
fixed in the linker.