This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: unwind question
On Wed, 2002-11-20 at 23:39, Martin v. Loewis wrote:
> 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.
>
Can someone explain the big difference between async an sync signals
(concerning exception tables)?
I guess the difference between sync and async signal is that i can avoid
sync signals by careful coding, so i can make sure that a peace of code
always works, and this is not possible with async signals?
But how does -fasynchronous-unwind-tables influence code generation (and
table generation)?
- Dietmar