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: Owen Taylor <otaylor at redhat dot com>, "libc-alpha at sources dot redhat dot com" <libc-alpha at sources dot redhat dot com>
Date: 20 Nov 2002 23:40:19 +0100
Subject: Re: unwind question
References: <1037808711.31081.43.camel@tequila><001c01c290b3$c94b82b0$f512e8d9@mira> <1037812202.31450.6.camel@tequila><20021120174201.077F5242C4E@fresnel.labs.redhat.com><1037819250.31864.13.camel@tequila>

Dietmar Maurer <dietmar@ximian.com> writes:

> So it really true that all libc functions either have unwind info, or
> they cant raise synchronous exceptions? 

That is the plan, yes, since it that requirement holds for C++, and
nobody has complained, yet.

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
- Re: unwind question
  - From: Owen Taylor
- 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]