|
From: Christian P. <tr...@ge...> - 2004-12-19 12:46:51
|
On Saturday 18 December 2004 7:23 pm, Tom Hughes wrote: > 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=3Dmemcheck .libs/lt-test-Con= sole > > > > [......] > > > > > 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. Have a look at [1], but griffon26 should have already sent this to your dev= =20 list already. What duo think about it? Regards, Christian Parpart. [1] http://dev.gentoo.org/~griffon26/valgrind-2.2.0-noexecstack.patch =2D-=20 Netiquette: http://www.ietf.org/rfc/rfc1855.txt 13:45:03 up 51 days, 6:15, 1 user, load average: 0.17, 0.06, 0.01 |