Re: [Valgrind-developers] Problem with executable stack on nptl-only systems

[Tom H. <th...@cy...>]

In message <200...@kf...>
          Maurice van der Pot <gri...@ge...> wrote:

> On Sat, Dec 18, 2004 at 06:46:01PM +0100, Maurice van der Pot wrote:
>
> > I've seen a few reports of the following problem:
> > 
> > http://bugs.gentoo.org/show_bug.cgi?id=74716
> > 
> > Basically, running valgrind on any executable on an nptl-only system
> > segfaults with the following message:
> > 
> >   error while loading shared libraries: libpthread.so.0: cannot enable
> >   executable stack as shared object requires: Invalid argument
> 
> Some additional info:
> The thing that requires an executable stack is the nested cleanup()
> function in __pthread_once() in vg_libpthread.c.

Right. I thought I'd got rid of all the nested functions...

I still don't understand why your system isn't just mapping the
stack as executable however. How you got some strange security
patch that completely blocks executable stacks or something?

Tom

-- 
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/