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: __attribute__ (__cleanup__) vs. _Unwind_Resume


Hello!

On Tue, Apr 21, 2009 at 12:48:09PM +0200, I wrote:
> On Mon, Apr 20, 2009 at 12:29:02PM -0700, Ulrich Drepper wrote:
> > Thomas Schwinge wrote:
> > > One possibility to fix this would be to add -lgcc_eh to libc.so-gnulib in
> > > Makeconfig (I don't know yet if that is legitimate), or perhaps, instead
> > > of that, we should introduce / use something like
> > > nptl/sysdeps/pthread/unwind-resume.c?
> > 
> > The later, probably.  This is how this work on Linux.
> 
> In fact, as it is enough to have a sysdeps/mach/hurd/unwind-resume.c à la
> ``#include "nptl/sysdeps/pthread/unwind-resume.c"'' (plus copying the
> three unwind-resume-referring lines from nptl/sysdeps/Makefile to
> sysdeps/mach/hurd/Makefile), and there being nothing NPTL-specific in
> unwind-resume.c (apart from the comment ``libgcc_s.so.1 must be installed
> for *pthread_cancel* to work''), I wonder if it wouldn't be fine to move
> that file to a generic location so that it can be picked up by every
> glibc port?  Or are there cases, where this unwinding support wouldn't be
> appropriate?
> 
> Additionally, couldn't this be unified with both
> nptl/sysdeps/pthread/unwind-forcedunwind.c and the libgcc_s handling in
> several backtrace.c files?

On Tue, Apr 21, 2009 at 02:08:15PM -0700, Roland McGrath wrote:
> I think it would be fine to move those files into sysdeps/gnu/.

Ulrich, what do you think?


Regards,
 Thomas

Attachment: signature.asc
Description: Digital signature


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