Bug 271337

Summary: Valgrind segfaults on MacOS X
Product: [Developer tools] valgrind Reporter: Goffredo Marocchi <Panajev>
Component: generalAssignee: Julian Seward <jseward>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version First Reported In: 3.7 SVN   
Target Milestone: ---   
Platform: MacPorts   
OS: macOS   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Goffredo Marocchi 2011-04-20 10:28:06 UTC 
Version:           3.7 SVN
OS:                OS X

I am running the default 32 bits kernel, I have Xcode 4.0.2 installed, and I installed valgrind through the Macports system (sudo port install valgrind/valgrind-devel). Neither the stable 3.6.1 version nor the valgrind-devel @3.7.0-r11524_0 one do seem to be able to even report the version number.

$ valgrind --version
Segmentation fault


Reproducible: Always

Steps to Reproduce:
$ valgrind --version



Actual Results:  
Segmentation fault

Expected Results:  
version number...
Comment 1 Julian Seward 2011-04-20 10:56:19 UTC 
Probably a duplicate of bug 267997.  Try checking out and building
the SVN trunk.
Comment 2 Goffredo Marocchi 2011-04-20 10:58:17 UTC 
As I was saying, this happens with 3.7.0-r11524_0, is this such an outdated version?
Comment 3 Julian Seward 2011-04-20 11:07:58 UTC 
Yes.  The fix is in r11686.
Comment 4 Goffredo Marocchi 2011-04-20 12:51:13 UTC 
$ valgrind --version
valgrind-3.7.0.SVN

Ok, thank you. Hopefully the Macports guys update the devel package soon :).
Comment 5 Julian Seward 2011-04-20 12:59:04 UTC 
(In reply to comment #4)
> Ok, thank you. Hopefully the Macports guys update the devel package soon :).

Maybe you could mail them and ask them to do so?

-------

Re-closing as a dup of 267997.

*** This bug has been marked as a duplicate of bug 267997 ***
Comment 6 Goffredo Marocchi 2011-04-20 13:00:31 UTC 
I will, I just did not want to bugger them too and make more people waste their time hehe :).