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: Jakub Jelinek <jakub at redhat dot com>
To: Owen Taylor <otaylor at redhat dot com>
Cc: Dietmar Maurer <dietmar at ximian dot com>, 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 21:16:23 +0100
Subject: Re: unwind question
References: <1037808711.31081.43.camel@tequila> <001c01c290b3$c94b82b0$f512e8d9@mira> <103 <20021120174201.077F5242C4E@fresnel.labs.redhat.com> <1037819250.31864.13.camel@tequila> <20021120195709.E6B58242CA5@fresnel.labs.redhat.com>
Reply-to: Jakub Jelinek <jakub at redhat dot com>

On Wed, Nov 20, 2002 at 02:57:09PM -0500, Owen Taylor wrote:
> > So it really true that all libc functions either have unwind info, or
> > they cant raise synchronous exceptions? 
> 
> I see no reason to doubt that.. :-) Of course very few libc
> functions actually have callbacks.

And those which do are usually compiled with -fexceptions.

	Jakub

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

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