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: martin at v dot loewis dot de (Martin v. Loewis)
To: Dietmar Maurer <dietmar at ximian dot com>
Cc: "libc-alpha at sources dot redhat dot com" <libc-alpha at sources dot redhat dot com>
Date: 20 Nov 2002 23:39:01 +0100
Subject: Re: unwind question
References: <1037808711.31081.43.camel@tequila><001c01c290b3$c94b82b0$f512e8d9@mira><1037812202.31450.6.camel@tequila>

Dietmar Maurer <dietmar@ximian.com> writes:

> Thats wrong. Any asynchrounous signal can interrupt any code, so this is
> a real problem for us.

If you need to plan for unwinding from asynchronous signals,
-fexceptions is not good enough. You also need to
-fasynchronous-unwind-tables. Be prepared for some size increase.

Regards,
Martin

Follow-Ups:
- Re: unwind question
  - From: Dietmar Maurer

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]