|
From: Tom H. <th...@cy...> - 2004-12-18 18:23:15
|
In message <200...@ge...>
Christian Parpart <tr...@ge...> wrote:
> On Wednesday 08 December 2004 2:42 pm, Christian Parpart wrote:
>
> > I really tried to invoke valgrind with different tools in order to
> > (initially) profile my applications. However, any application in any
> > valgrind argument combination lets valgrind die with a message like
> >
> > "cannot enable executable stack as shared object requires: Invalid
> > argument"
> >
> > Below is the ouput of one valgrind test:
> >
> > trapni@battousai tests $ valgrind --tool=memcheck .libs/lt-test-Console
> [......]
> > Segmentation fault
> > trapni@battousai tests $
> >
> > Can someone help me please?
>
> VALGRIND doesn't run on an NPTL-only system. thanks for your help ;-)
I know of no reason why it shouldn't. We have supported NPTL for some
time now - in fact NPTL itself was never really the problem, the problem
was the change in the TLS model.
I don't see what executable stacks has to do with NPTL anyway?
That executable stack issue looks like a dynamic linker problem
anyway - why is the dynamic linker reporting EINVAL trying to load
a library that needs an executable stack?
I have to say I;m not sure offhand why the linker has decided
that libpthread.so needs an executable stack so I'll have to
look at that - it may just be that it pulls in some assembly
code that hasn't been properly tagged.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|