[LLVMbugs] [Bug 23166] New: Segmentation fault in llvm-symbolizer on missing compile units
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Wed Apr 8 19:48:57 PDT 2015
https://llvm.org/bugs/show_bug.cgi?id=23166
Bug ID: 23166
Summary: Segmentation fault in llvm-symbolizer on missing
compile units
Product: new-bugs
Version: 3.6
Hardware: Macintosh
OS: All
Status: NEW
Severity: normal
Priority: P
Component: new bugs
Assignee: unassignedbugs at nondot.org
Reporter: me at cirw.in
CC: llvmbugs at cs.uiuc.edu
Classification: Unclassified
0 llvm-symbolizer 0x00000001064f6839
llvm::sys::PrintStackTrace(__sFILE*) + 57
1 llvm-symbolizer 0x00000001064f6f9b SignalHandler(int) + 635
2 libsystem_platform.dylib 0x00007fff93515f1a _sigtramp + 26
3 libsystem_platform.dylib 0x000000000005d12a _sigtramp + 1823765034
4 llvm-symbolizer 0x00000001063c2530
llvm::DWARFUnit::collectAddressRanges(std::__1::vector<std::__1::pair<unsigned
long long, unsigned long long>, std::__1::allocator<std::__1::pair<unsigned
long long, unsigned long long> > >&) + 64
5 llvm-symbolizer 0x00000001063b21f1
llvm::DWARFDebugAranges::generate(llvm::DWARFContext*) + 257
6 llvm-symbolizer 0x00000001063aaf43
llvm::DWARFContext::getCompileUnitForAddress(unsigned long long) + 195
7 llvm-symbolizer 0x00000001063ab6fc
llvm::DWARFContext::getInliningInfoForAddress(unsigned long long,
llvm::DILineInfoSpecifier) + 92
8 llvm-symbolizer 0x000000010639ddd4
llvm::symbolize::ModuleInfo::symbolizeInlinedCode(unsigned long long,
llvm::symbolize::LLVMSymbolizer::Options const&) const + 132
9 llvm-symbolizer 0x000000010639e224
llvm::symbolize::LLVMSymbolizer::symbolizeCode(std::__1::basic_string<char,
std::__1::char_traits<char>, std::__1::allocator<char> > const&, unsigned long
long) + 116
10 llvm-symbolizer 0x00000001063a4865 main + 1525
11 libdyld.dylib 0x00007fff96ae45c9 start + 1
Stack dump:
0. Program arguments: ./llvm/Release+Asserts/bin/llvm-symbolizer
-obj=segfaulty
[1] 32676 done echo 0xb6f74 |
32677 segmentation fault ./llvm/Release+Asserts/bin/llvm-symbolizer
-obj=segfaulty
If you run llvm-dwarfdump on this file you get an assertion failure, which
seems reasonable:
Assertion failed: (CU && "Null Compile Unit?"), function dump, file
DWARFCompileUnit.cpp, line 26.
0 llvm-dwarfdump 0x00000001033978a9
llvm::sys::PrintStackTrace(__sFILE*) + 57
1 llvm-dwarfdump 0x000000010339800b SignalHandler(int) + 635
2 libsystem_platform.dylib 0x00007fff93515f1a _sigtramp + 26
3 llvm-dwarfdump 0x00000001033ba69d nuls + 3413
4 llvm-dwarfdump 0x0000000103397d76 abort + 22
5 llvm-dwarfdump 0x0000000103397d51 __assert_rtn + 81
6 llvm-dwarfdump 0x000000010334bc05
llvm::DWARFCompileUnit::dump(llvm::raw_ostream&) + 885
7 llvm-dwarfdump 0x000000010334be2b
llvm::DWARFContext::dump(llvm::raw_ostream&, llvm::DIDumpType) + 475
8 llvm-dwarfdump 0x00000001033488bb main + 1195
9 libdyld.dylib 0x00007fff96ae45c9 start + 1
10 libdyld.dylib 0x0000000000000002 start + 1766963770
Stack dump:
0. Program arguments: ./llvm/Release+Asserts/bin/llvm-dwarfdump segfaulty
[1] 32568 illegal hardware instruction
./llvm/Release+Asserts/bin/llvm-dwarfdump segfaulty > /dev/null
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20150409/0bd89756/attachment.html>
More information about the llvm-bugs
mailing list