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]

Threadsafe exception handling needed even if no exceptions used?


Hi,

I think I've just tracked down a very erratic bug in one of my
programs, which only appears on Irix6 with egcs-1.0.3 -- on Linux
everything was/is fine, even with the `old' egcs-1.0.3.  Now I'd like
to confirm the possible cause before upgrading to 1.1.1.

I'm using threads from C++, but no exceptions (though I have _not_
compiled all my code with `-fno-exceptions').

It seems that after creating a thread from a C++ function f(), very
rarely the content of __dynamic_handler_chain gets corrupted by the
created subthread, which leads to a crash in f(), even though no
exceptions are ever thrown or caught anywhere in the code.

I'd just like to confirm whether this explanation is plausible.

For bonus points, would consistently specifying `-fno-exceptions'
everywhere help?, and why does it only seem to happen on Irix (I
thought the exception handling was identical on Linux/all ELF
platforms) ?

Thanks,
Wolfram.
-- 
`Surf the sea, not double-u three...'
wmglo@dent.med.uni-muenchen.de


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