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: Nathan Sidwell <nathan at acm dot org>
To: Richard Henderson <rth at redhat dot com>
Cc: Nathan Sidwell <nathan at codesourcery dot com>, Roger Sayle <roger at eyesopen dot com>, gcc <gcc at gcc dot gnu dot org>, Anthony Green <green at redhat dot com>
Date: Tue, 03 Sep 2002 10:47:39 +0100
Subject: Re: Throwing C++ exceptions in signal handlers
References: <Pine.LNX.4.33.0209021500250.24609-100000@www.eyesopen.com> <3D73E1C5.B73739B@codesourcery.com> <20020903092916.GD8737@redhat.com>
Reply-to: nathan at compsci dot bristol dot ac dot uk

Richard Henderson wrote:

> With -fnon-call-exceptions it is.
I stand corrected. Roger, note that non-call-exceptions only allows
trapping instructions to throw exceptions (from the sig handler
they invoke). You can't throw from an arbitrary signal handler.

nathan

-- 
Dr Nathan Sidwell :: Computer Science Department :: Bristol University
           The voices in my head told me to say this
nathan@acm.org  http://www.cs.bris.ac.uk/~nathan/  nathan@cs.bris.ac.uk

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

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