|
From: William M. <wi...@dr...> - 2003-07-16 15:43:39
|
it happens with all programs i try RedHat 7.3 with grsec 2.4.21 kernel Gcc V 2.96 valgrind-1.0.4 just did ./configure then make then make install |
|
From: William M. <wi...@dr...> - 2003-07-16 16:16:09
|
valgrind.so: When searching for client's argc/argc/envp:
Cannot determine stack segment from /proc/self/maps
valgrind.so: Startup or configuration error:
couldn't find client's argc/argc/envp
valgrind.so: Unable to start up properly. Giving up.
now i get this when i do anything even just type valgrind i installed the
new version
|
|
From: Dan K. <da...@ke...> - 2003-07-16 16:04:43
|
William McInnis wrote: > it happens with all programs i try > RedHat 7.3 with grsec 2.4.21 kernel > Gcc V 2.96 > valgrind-1.0.4 > just did ./configure then make then make install valgrind-1.0.4 is very out of date. Please try the latest, valgrind-1.9.6. - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045 |
|
From: Steve G <lin...@ya...> - 2003-07-16 16:20:09
|
>RedHat 7.3 with grsec 2.4.21 kernel The grsec kernel does a lot of things to prevent security related attacks. I suspect they've got a different program layour when fork/execv is called. Try booting the normal Red Hat kernel for the software devlopment and see if that fixes your problem. Best Regards, -Steve Grubb __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com |
|
From: Julian S. <js...@ac...> - 2003-07-16 18:07:32
|
On Wednesday 16 July 2003 17:20, Steve G wrote: > >RedHat 7.3 with grsec 2.4.21 kernel > > The grsec kernel does a lot of things to prevent security > related attacks. I suspect they've got a different program > layour when fork/execv is called. > > Try booting the normal Red Hat kernel for the software > devlopment and see if that fixes your problem. That probably will fix the problem -- which is that /proc/self/maps isn't readable on the grsec kernel, I guess. J |