[MacPorts] #57737: llvm-3.9 built with clang-3.4 segfaults when used with clang-3.9, but llvm-3.9 built with clang-3.7 works correctly

MacPorts noreply at macports.org
Thu Dec 6 21:45:17 UTC 2018


#57737: llvm-3.9 built with clang-3.4 segfaults when used with clang-3.9, but
llvm-3.9 built with clang-3.7 works correctly
--------------------+----------------------
 Reporter:  kencu   |      Owner:  jeremyhu
     Type:  defect  |     Status:  assigned
 Priority:  Normal  |  Milestone:
Component:  ports   |    Version:
 Keywords:          |       Port:  llvm-3.9
--------------------+----------------------
 Noticed when building newer clang versions on Leopard:
 {{{
 Date/Time:       2018-11-29 16:54:34.484 -0800
 OS Version:      Mac OS X Server 10.5.8 (9L34)
 Report Version:  6
 Anonymous UUID:  8AD195D0-D2E5-4A89-A13F-9829EBFB058B

 Exception Type:  EXC_BAD_ACCESS (SIGBUS)
 Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000001
 Crashed Thread:  0

 Thread 0 Crashed:
 0   libLLVM.dylib                       0x023066a5
 llvm::SmallPtrSetImplBase::Grow(unsigned int) + 93
 1   libLLVM.dylib                       0x02306643
 llvm::SmallPtrSetImplBase::insert_imp_big(void const*) + 139
 2   clang                               0x003dbe67
 llvm::SmallPtrSetImplBase::insert_imp(void const*) + 131
 3   clang                               0x005a7740
 llvm::SmallPtrSetImpl<clang::Decl*>::insert(clang::Decl*) + 32
 4   clang                               0x006b3b05
 clang::Sema::PushOnScopeChains(clang::NamedDecl*, clang::Scope*, bool) +
 459
 }}}

 rebuilding llvm-3.9 with clang-3.7 results in a functionally working
 system.

 So based on this, clang-3.4 was blacklisted when building llvm-3.9 or
 newer.

 My apologies, Jeremy -- I should have waited longer for you to review this
 issue before bumping the commit from the PR list.

-- 
Ticket URL: <https://trac.macports.org/ticket/57737>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list