Bugzilla – Bug 104181
valgrind dies on start
Last modified: 2005-08-12 11:31:00 UTC
valgrind --tool=memcheck ls <bang> It'd also be nice if the (faster) 'addrcheck' module was installed & usable.
I guess it's some obscure 3.0.0 bug :-) but since it doesn't work at all - perhaps 2.4.1 would be nice instead ?
There's a valgrind2 package for this.
your test case works fine for me. Valgrind 3.0.0 works execllent on my beta1. What is the "bang" here?
Created attachment 45860 [details] my effort
So - I guess this is my personal build of up-stream 3.0.0 - which behaves in the same way - I guess it may be some CPU specific thing then. I'll re-file with Julian.
very weird. SIGILL would only hit in valgrind's own code, no? And a duron should not be the most adventures hardware - I tried on a p4 though
its a known bug - valgrind 3.0 requries SSE. It has been fixed already, but it requries an update. BTW addrcheck doesn't exist anymore with valgrind 3.0. memcheck is faster instead.
fixed for stable (I do wonder where you found the package though since its still in state candidate).
Julian says: > VALGRIND_3_0_BRANCH is the stable branch leading to 3.0.1 so it should > prove as stable or more so than 3.0.0, and should be good for production > use. and it's fixed there :-) I found the package on my SUSE 10.0 Beta1 CD set ;-)