Bug 283325

Summary:	Valgrind segfaults on startup on OSX 10.6.7 when built with Xcode 4.0
Product:	[Developer tools] valgrind	Reporter:	James Abley <james.abley>
Component:	general	Assignee:	Julian Seward <jseward>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	3.6.0
Target Milestone:	---
Platform:	unspecified
OS:	macOS
Latest Commit:		Version Fixed In:

Description James Abley 2011-10-04 16:12:31 UTC

Version:           3.6.0
OS:                OS X

The reported version should be 3.6.1, but that isn't available as a version to report a bug against in this bug tracker.

I think this is distinct from https://bugs.kde.org/show_bug.cgi?id=267997

Initially reported to Homebrew as https://github.com/mxcl/homebrew/issues/7895

Trying to install 3.6.1 on Snow Leopard 10.6.8, running Xcode 4.0.

I installed via Homebrew. Building with both GCC and LLVM gave the crash.

$ valgrind --help

or any other attempt to run the application crashed.

Running `/Developer/Library/uninstall-devtools --mode=all` and installing Xcode 3.2.6 enabled me to build a version of valgrind that works properly.

I have a core dump available if that would help. I don't know the C toolchain well enough to do much with it (but I'm learning!).

Reproducible: Always

Steps to Reproduce:
$ valgrind --help
$ valgrind ./ex1


Actual Results:  
valgrind segfaults

Expected Results:  
no segfault

Comment 1 Julian Seward 2011-10-05 06:55:34 UTC

> I think this is distinct from https://bugs.kde.org/show_bug.cgi?id=267997

Why do you say that?  I think this is identical to 267997.

Comment 2 James Abley 2011-10-05 11:57:54 UTC

My reading of 267997 is it was reported against 3.6.0, is now fixed, and 3.6.1 available via Homebrew incorporates that fix. The last reported problem in 267997 is that it fails to build [1]. I wasn't seeing a build failure; I was seeing a segfault from running the application, so I assumed it was something new.

[1] https://bugs.kde.org/show_bug.cgi?id=267997#c18

Comment 3 Julian Seward 2011-10-07 09:07:33 UTC


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