This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: unwind question
- From: Dietmar Maurer <dietmar at ximian dot com>
- To: "Martin v." Löwis <martin at v dot loewis dot de>
- Cc: "libc-alpha at sources dot redhat dot com" <libc-alpha at sources dot redhat dot com>
- Date: 20 Nov 2002 18:10:02 +0100
- Subject: Re: unwind question
- References: <1037808711.31081.43.camel@tequila> <001c01c290b3$c94b82b0$f512e8d9@mira>
On Wed, 2002-11-20 at 17:42, Martin v. Löwis wrote:
> > But I soon detected that there is no unwinding information available
> for
> > functions contained inside libc. So if an exception occurs inside
> those
> > function it is impossible to unwind the stack, even when they are
> called
> > from function which has unwinding information?
> >
> > Is this true, or is there a way to solve that somehow?
>
> Yes, and no. Those functions that can cause exceptions
> (i.e. those that call back user code) are compiled with -fexception
> (qsort being the most prominent example). You should not need
> to worry about the functions that have no unwind information since
> you will never see them on your stack.
Thats wrong. Any asynchrounous signal can interrupt any code, so this is
a real problem for us.
- Dietmar