Bug 104181 - valgrind dies on start
Summary: valgrind dies on start
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: ConsoleApps (show other bugs)
Version: Beta 1
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-11 16:24 UTC by Michael Meeks
Modified: 2005-08-12 11:31 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
my effort (1.38 KB, text/plain)
2005-08-12 08:39 UTC, Michael Meeks
Details

Note You need to log in before you can comment on or make changes to this bug.
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 ;-)