Bug 274784

Summary:	valgrind ls -l or any other valgrind call(even without parameters) results in Segmentation Fault
Product:	[Developer tools] valgrind	Reporter:	Herbert Grasberger <grassi>
Component:	general	Assignee:	Julian Seward <jseward>
Status:	RESOLVED DUPLICATE
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	macOS
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	./configure and make log

Description Herbert Grasberger 2011-06-02 22:05:17 UTC

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.

Comment 1 pbholmen 2011-06-06 16:05:34 UTC

Created attachment 60699 [details]
./configure and make log

Comment 2 pbholmen 2011-06-06 16:08:17 UTC

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".

Comment 3 Julian Seward 2011-06-06 17:31:53 UTC

This was fixed in the trunk about a month ago.

*** This bug has been marked as a duplicate of bug 267997 ***

Comment 4 pbholmen 2011-06-06 18:55:53 UTC

Thanks. Should I run the patch you proposed in bug 267997, or wait for it to 
enter a stable release?

Comment 5 Julian Seward 2011-06-08 01:01:32 UTC

Neither.  Instead just check out and build the trunk, as described at
http://www.valgrind.org/downloads/repository.html