Version: unspecified OS: OS X I downloaded the current 3.6.1 Release (the list only had 3.6.0, thus I left it unspecified) and followed the compiling and installation instructions as stated in the readme. I did not pass additional parameters to ./configure. After the make install phase I tested valgrind with "ls -l" and it resulted in a segmentation fault. So does any other call to valgrind. uname -a on my machine produces: Darwin douglasfir.cs.uvic.ca 10.7.0 Darwin Kernel Version 10.7.0: Sat Jan 29 15:17:16 PST 2011; root:xnu-1504.9.37~1/RELEASE_I386 i386 g++ --version produces: i686-apple-darwin10-g++-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3) valgrind -v only produces the Segmentation Fault message, nothing else. Reproducible: Always Steps to Reproduce: call valgrind Actual Results: Segmentation Fault I recently upgraded to the newest Xcode Tools version (4.0.2) which might have modified the compiler or glibc. I don't know if valgrind would have run before that, since I haven't used it yet, but I thought it might be valuable information.
Created attachment 60699 [details] ./configure and make log
I can confirm this bug. XCode version 4.0.2 build 4A2002a, Mac OS X version 10.6.7, Intel Core i5 2.4 GHz. All calls to valgrind immediately quits with the following message "Segmentation fault".
This was fixed in the trunk about a month ago. *** This bug has been marked as a duplicate of bug 267997 ***
Thanks. Should I run the patch you proposed in bug 267997, or wait for it to enter a stable release?
Neither. Instead just check out and build the trunk, as described at http://www.valgrind.org/downloads/repository.html