Bug 104181

Summary: valgrind dies on start
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Michael Meeks <mmeeks>
Component: ConsoleAppsAssignee: E-mail List <kde-maintainers>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Beta 1   
Target Milestone: ---   
Hardware: Other   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: my effort

Description Michael Meeks 2005-08-11 16:24:24 UTC 
valgrind --tool=memcheck ls
<bang>

It'd also be nice if the (faster) 'addrcheck' module was installed & usable.
Comment 1 Michael Meeks 2005-08-11 16:31:26 UTC 
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 ?
Comment 2 Andreas Jaeger 2005-08-11 19:41:34 UTC 
There's a valgrind2 package for this.
Comment 3 Stephan Kulow 2005-08-12 08:23:32 UTC 
your test case works fine for me. Valgrind 3.0.0 works execllent on my beta1. 
What is the "bang" here?
Comment 4 Michael Meeks 2005-08-12 08:39:03 UTC 
Created attachment 45860 [details]
my effort
Comment 5 Michael Meeks 2005-08-12 08:39:52 UTC 
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.
Comment 6 Stephan Kulow 2005-08-12 09:02:22 UTC 
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
Comment 7 Dirk Mueller 2005-08-12 09:35:34 UTC 
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.
Comment 8 Dirk Mueller 2005-08-12 10:55:36 UTC 
fixed for stable (I do wonder where you found the package though since its 
still in state candidate).
Comment 9 Michael Meeks 2005-08-12 11:31:00 UTC 
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 ;-)