clang-3.8 crashes dsymutil with -gdwarf-4 on 10.9

[Jeremy Huddleston Sequoia]

What's the output of this on your system:

   /usr/bin/dsymutil --version

I don't see the issue using current versions (llvm-3.8+, Xcode 8.x) of llvm-dsymutil.  I suspect the issue here is that we should be updating the driver to use its llvm-dsymutil instead of /usr/bin/dsymutil.

Please file a ticket.

--Jeremy

> On Feb 26, 2017, at 02:51, Mihai Moldovan <ionic at macports.org> wrote:
> 
> Actually, this is enough to trigger an assertion failure (albeit a different one):
> 
> <-----snip----->
> #include <cstdlib>
> #include <iostream>
> 
> int main (int argc, char **argv) {
> std::cerr << std::endl;
> 
> return (EXIT_SUCCESS);
> }
> <-----snip----->
> 
> Assertion failed: (linked_addr_pos != line_table_map.end()), function FixReferences, file /SourceCache/dwarf_utilities/dwarf_utilities-119/source/DWARFdSYM.cpp, line 3749.
> 
> Tested and reproduced with both clang 3.7 and 3.8.
> 
> Unreproducible with Xcode clang.
> 
> When compiled with clang 3.9, dsymutil spews out warnings, but *doesn't* trip on an assertion:
> 
> warning: {0x00004026} TAG_formal_parameter:  AT_location( 0x001fdc11 ) didn't have valid function low pc, the location list will be incorrect.
> warning: {0x00004054} TAG_formal_parameter:  AT_location( 0x00002f91 ) didn't have valid function low pc, the location list will be incorrect.
> 
> 
> 
> Mihai
>