clang-3.7 @3.7.1_3+analyzer, llvm-3.7 @3.7.1_3 crash due to segmentation fault

[kenneth.f.cunningham@…]

10.6.8 / libc++

segmentation fault on any use, crash log attached. Reverting to last llvm-3.7 version works OK again.

[kenneth.f.cunningham@…]

filed upstream as <​https://llvm.org/bugs/show_bug.cgi?id=28592> as I presume this is an upstream bug.

[jeremyhu (Jeremy Huddleston Sequoia)]

There wasn't anything substantially different between the current and previous revision (just changes for additional 'port select' symlinks'. There should be no difference in the binaries.

[kenneth.f.cunningham@…]

Noted. Given that, perhaps there is an inconsistency on this end, then, as I have several llvm & clang versions installed. Will see if I can sort it out. Thanks.

[kenneth.f.cunningham@…]

This issue turned out to be a local problem, and was ultimately repaired by deactivating / uninstalling all versions of clang, llvm, cctools, and ld64, resetting macports.conf and variants.conf back to original settings, and then following the "lib++ on older systems" instructions from the beginning again.

Some inconsistency between versions of these tools must have developed over time.

Thanks. Sorry for the unnecessary ticket. K.

[mojca (Mojca Miklavec)]

Cc Me!

[mojca (Mojca Miklavec)]

I just wanted to add that I had a perfectly working clang 3.7 until a few days ago. I'm using the default MP installation (stdlibc++) on 10.7. This is what's crashing for me since the latest updates:

Process:         ld-latest [46035]
Path:            /opt/local/libexec/*/ld-latest
Identifier:      ld-latest
Version:         ??? (???)
Code Type:       X86-64 (Native)
Parent Process:  clang [46033]

Date/Time:       2016-08-01 20:04:27.079 +0200
OS Version:      Mac OS X 10.7.5 (11G63b)
Report Version:  9

Crashed Thread:  0

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: @executable_path/../lib/libLTO.dylib
  Referenced from: /opt/local/libexec/*/ld
  Reason: Incompatible library version: ld requires version 1.0.0 or later, but libLTO.dylib provides version 0.0.0

Binary Images:
       0x10343d000 -        0x103590ff7 +ld (??? - ???) <F45CBD4F-6BE3-3FE9-93B5-E3EDDB233A9C> /opt/local/libexec/*/ld
       0x103648000 -        0x103659fff +libLTO.dylib (??? - ???) <94DDE183-064B-3616-A3AD-35107AF420B4> /opt/local/libexec/*/libLTO.dylib
    0x7fff6303d000 -     0x7fff63071baf  dyld (195.6 - ???) <0CD1B35B-A28F-32DA-B72E-452EAD609613> /usr/lib/dyld

I didn't try to reinstall MP yet.

[mojca (Mojca Miklavec)]

... but I just noticed that r150880 insists in installing some ports universal. I'll try that.

But the major problem seems that macports is trying to upgrade llvm-3.7 with a broken clang-3.7 compiler. Most likely

sudo port install llvm-3.7 configure.compiler=macports-clang-3.6

will help.

[jeremyhu (Jeremy Huddleston Sequoia)]

That has nothing to do with this issue. You're seeing #51929.

[mojca (Mojca Miklavec)]

I was aware of that issues. The only problem is that the upgrade process (intended to address the issue #51929) is using the broken compiler in the absence of manual intervention.

The weird thing is that

sudo port upgrade clang-3.7

first installed clang-3.6, but then used the broken clang-3.7 to upgrade llvm-3.7.