[MacPorts] #56883: gdb @8.0.1: Please consider extending gdb's compiler blacklist to include Apple LLVM version 5.1 (clang-503.0.40)
MacPorts
noreply at macports.org
Sat Jul 28 16:47:40 UTC 2018
#56883: gdb @8.0.1: Please consider extending gdb's compiler blacklist to include
Apple LLVM version 5.1 (clang-503.0.40)
-----------------------------------------+--------------------
Reporter: Hexchild | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.5.3
Keywords: gdb ada-lang segfault crash | Port: gdb
-----------------------------------------+--------------------
The clang++ binary crashes on my machine while building the gdb package.
This issue appears to be 100% reproducible, whether or not I run "sudo
port clean gdb".
I have Xcode 5.1.1 on Mavericks (OSX 10.9.4):
{{{
$ clang++ --version
Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)
Target: x86_64-apple-darwin13.3.0
Thread model: posix
}}}
The culprit seems to be ada-lang.c (less relevant walls of text replaced
with "..." for the sake of brevity):
{{{
$ cd /opt/local/var/macports/build/ ...
_ports_devel_gdb/gdb/work/gdb-8.0.1/gdb
$ sudo /usr/bin/clang++ ... ada-lang.c
...
Stack dump:
0. Program arguments: ... ada-lang.c
1. <eof> parser at end of file
2. Per-module optimization passes
3. Running pass 'CallGraph Pass Manager' on module 'ada-lang.c'.
4. Running pass 'SROA' on function
'@_ZL25ada_add_global_exceptionsP17re_pattern_bufferPP16VEC_ada_exc_info'
clang: error: unable to execute command: Segmentation fault: 11
...
}}}
I have verified that the macports llvm-6.0 version of clang++ does not
crash when compiling this file on my system.
I see this was done in gdb's port file:
{{{
# clang 600.0.57 is known to segfault when building this
compiler.blacklist {clang >= 600 < 601}
}}}
Added here:
{{{
commit 30580e00386a4e862a2ba6654eac4a222d0a3ded
Author: Ryan Schmidt <ryandesign at macports.org>
Date: Fri Nov 17 10:58:00 2017 -0600
gdb: Blacklist clang 600
}}}
I highly suspect I have the same issue but with a different LLVM version,
however I can't be sure since I can't find a ticket for the above change.
Regardless, the crash I'm seeing should probably be avoided.
--
Ticket URL: <https://trac.macports.org/ticket/56883>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list