This is the mail archive of the libc-alpha@sourceware.org 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: exception handling predicament

From: "H.J. Lu" <hjl.tools@gmail.com>
Date: Fri, 19 Aug 2011 07:07:28 -0700

> Is this related to:
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48338

I think that commit you triaged this GCC bug to is just exposing the
issue and not the true cause.

You may want to mention my analysis in that bug report.

The big question is whether __cleanup__ can be used when exceptions
(and thus the unwind) could be triggerd asynchronously.  I think it is
not designed to do so, and therefore __cleanup__ cannot be used in
this aio_suspend.c situation.

I think GCC is behaving properly.

I'm seeing this trigger with gcc-4.6.1 on sparc, FWIW.
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]