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]

Re: Throwing C++ exceptions in signal handlers

From: Richard Henderson <rth at redhat dot com>
To: Nathan Sidwell <nathan at codesourcery dot com>
Cc: Roger Sayle <roger at eyesopen dot com>, gcc <gcc at gcc dot gnu dot org>
Date: Tue, 3 Sep 2002 02:29:16 -0700
Subject: Re: Throwing C++ exceptions in signal handlers
References: <Pine.LNX.4.33.0209021500250.24609-100000@www.eyesopen.com> <3D73E1C5.B73739B@codesourcery.com>

On Mon, Sep 02, 2002 at 11:10:13PM +0100, Nathan Sidwell wrote:
> > Might it be safer to comment out "raise" in cp/cfns.gperf, or is
> > throwing an exception in a signal handler explicitly forbidden?
> It is not permitted.

With -fnon-call-exceptions it is.

And yes there would appear to be a problem if the call to
raise gets nothrow attached with this option in effect.

r~

Follow-Ups:
- Re: Throwing C++ exceptions in signal handlers
  - From: Nathan Sidwell

References:
- Throwing C++ exceptions in signal handlers
  - From: Roger Sayle
- Re: Throwing C++ exceptions in signal handlers
  - From: Nathan Sidwell

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