This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Potential link or compiler bug


I am compiling my .so file on a Linux Redhat 6.2 system with the latest
updates to glibc using c++ version egcs-2.91.66 with the following options:

-fPIC -fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith
-Wbad-function-cast -Wcast-align -Woverloaded-virtual -Wsynth -Wshadow
-pedantic -Wno- long- long -pthread

And linking with the following options:

-fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith
-Wbad-function-cast -Wcast-align -Woverloaded-virtual -Wsynth -Wshadow
-pedantic -Wno- long- long -pthread -shared 

I get no errors or warnings but when my application tries to open my .so it
seg faults on the following call:

_dl_relocate_object()

Before I added a bunch of void do nothing methods to my class in attemp to
add a buffer around my "real" methods (someone suggested this) it seg
faulted on:

_dl_lookup_symbol()

and the pointer to the undefined name was out of bounds.

I've compiled my library on a RedHat 7.0 system and it appears to not have
the above problem because I can do a ldd -d and ldd -r without either one
core dumping like on my RedHat 6.2 system.

Does anyone know if this might be a bug in the compiler or linker or
suggestions on something I could fix in my code?

Any help is most appreciated!!
Sharon Bregante-Candau

Opinions expressed are those of the author and do not represent Intel
Corporation.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]