This is the mail archive of the gcc@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]
Other format: [Raw text]

--enable-__cxa_atexit and gcc 3.1.1 release.


Hello,

I have multi-threading app which is crashing while throwing exception in
libstdc++ and which I've compile with gcc 3.1.1:

thinkpad:~$ c++ -v
Reading specs from
/home/karel/usr/local/fake-gcc3.1.1/bin/../lib/gcc-lib/i686-pc-linux-gnu/3.1.1/specs
Configured with: /home/karel/cvs/gcc/gcc3.1/configure
--prefix=/home/karel/usr/local/gcc3.1.1 --enable-shared --enable-threads
--enable-languages=c++ --program-prefix=a
Thread model: posix
gcc version 3.1.1
thinkpad:~$


After going through the gcc mailing list archive I've found interesting
configure option: '--enable-__cxa_atexit' and so I've tried to compile gcc
3.1.1 with this option. Now when using gcc configured:

thinkpad:~/cvs/csiv2-l1-work/mico/demo/ccm/hello2$ c++ -v
Reading specs from
/home/karel/usr/local/gcc3.1.1cxa_atexit/lib/gcc-lib/i686-pc-linux-gnu/3.1.1/specs
Configured with: /home/karel/cvs/gcc/gcc3.1/configure
--prefix=/home/karel/usr/local/gcc3.1.1cxa_atexit --enable-shared
--enable-threads --enable-languages=c++ --program-prefix=a
--enable-__cxa_atexit
Thread model: posix
gcc version 3.1.1
thinkpad:~/cvs/csiv2-l1-work/mico/demo/ccm/hello2$

the app is stable.

Platform is Debian GNU/Linux 3.0, glibc 2.2.5, binutils 2.12.90.0.1
20020307 Debian/GNU Linux.

My simple question is: is it possible that this configure option help in
this crashing, or have I to find the problem somewhere else?

I'm able to provide you with more info, just don't know with which.

Thanks a lot,

Karel
--
Karel Gardas                  kgardas@objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com


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