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]

Re: c++ exceptions and signals


In article <Pine.LNX.4.02.9901111253120.3852-100000@eraser.physik.uni-konstanz.de>,
pmaunz@eraser.physik.uni-konstanz.de (Peter Maunz) writes:
> Hallo
> I'm using egcs 1.1.1 on a SuSE 5.3 linux PII
> and want to use signals (like SIGTERM)
> by throwing an exception.

Asynchronous exceptions are not supported in egcs. You are out of
luck.  The compiler "knows" which statements (function calls etc) are
able to throw exceptions and generates the necessary cleanup code to
handle destructors etc for these regions. With asynchronous exceptions
this assumption breaks and you'll most likely get serious data corruption.

There is a -fasynchronous-exceptions flag in egcs 1.1.1, but AFAIK it is
not finished and unsupported.

So you are out of luck. 

-Andi


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