This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc 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: unwind question

From: Richard Henderson <rth at twiddle dot net>
To: Dietmar Maurer <dietmar at ximian dot com>
Cc: Martin v. Löwis <martin at v dot loewis dot de>, "libc-alpha at sources dot redhat dot com" <libc-alpha at sources dot redhat dot com>
Date: Wed, 20 Nov 2002 23:15:35 -0800
Subject: Re: unwind question
References: <1037808711.31081.43.camel@tequila> <001c01c290b3$c94b82b0$f512e8d9@mira> <1037812202.31450.6.camel@tequila>

On Wed, Nov 20, 2002 at 06:10:02PM +0100, Dietmar Maurer wrote:
> Thats wrong. Any asynchrounous signal can interrupt any code, so this is
> a real problem for us.

You're fooling yourself (or generating really bulky slow code) 
if you are attempting to handle truely asynchrounous exceptions.

GCC doesn't support this notion for exactly this reason.
We _do_ support synchrounous exceptions from SIGSEGV, SIGFPE
and the like, but SIGALRM is right out.

r~

References:
- unwind question
  - From: Dietmar Maurer
- Re: unwind question
  - From: Martin v. Löwis
- Re: unwind question
  - From: Dietmar Maurer

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