Summary: | valgrind segfaults immediately (segmentation fault) | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Pete Stevenson <jpeter> |
Component: | general | Assignee: | Julian Seward <jseward> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | mike |
Priority: | NOR | ||
Version: | 3.6.0 | ||
Target Milestone: | --- | ||
Platform: | MacPorts | ||
OS: | macOS | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Pete Stevenson
2011-03-28 22:21:22 UTC
It's not certainly a 64-bit kernel. Looks like a dupe of http://bugs.kde.org/show_bug.cgi?id=267997, can you reproduce the same output with the same flags? Are you using XCode 4.0.x to build Valgrind? I can reproduce this problem using Xcode 4 (outside of Macports). Reason I ask is, this is not the first time I've heard of this. My working theory is that is segfaults when built by Xcode 4 but not Xcode 3. However, I don't have a copy of 4, so it would be good if someone who does, can verify this theory. I've just uninstalled Xcode 4, installed Xcode 3 and it compiles and works fine. It's definitely that, even when you force it to use GCC rather than LLVM. If you have an OSX box then I'll Paypal you the cost of Xcode 4 if you want? I will confirm that I am using Xcode 4. I can reproduce this with xcode 4.0.1. Investigating. *** This bug has been marked as a duplicate of bug 267997 *** |