/home/omair.javaid/work/lldb/build/armhf/bin/lldb --no-lldbinit -S /home/omair.javaid/work/lldb/build/armhf/tools/lldb/test/Shell/lit-lldb-init /home/omair.javaid/work/lldb/build/armhf/tools/lldb/test/SymbolFile/DWARF/Output/dwarf5-debug_line-file-index.s.tmp -o "image lookup -f hello.c -l 1" (lldb) command source -s 0 '/home/omair.javaid/work/lldb/build/armhf/tools/lldb/test/Shell/lit-lldb-init' Executing commands in '/home/omair.javaid/work/lldb/build/armhf/tools/lldb/test/Shell/lit-lldb-init'. (lldb) # LLDB init file for the LIT tests. (lldb) settings set symbols.enable-external-lookup false (lldb) settings set plugin.process.gdb-remote.packet-timeout 60 (lldb) settings set interpreter.echo-comment-commands false (lldb) settings set symbols.clang-modules-cache-path "/home/omair.javaid/work/lldb/build/armhf/lldb-test-build.noindex/module-cache-lldb" (lldb) settings set target.auto-apply-fixits false (lldb) settings set target.inherit-tcc true (lldb) settings set target.detach-on-error false (lldb) target create "/home/omair.javaid/work/lldb/build/armhf/tools/lldb/test/SymbolFile/DWARF/Output/dwarf5-debug_line-file-index.s.tmp" Current executable set to '/home/omair.javaid/work/lldb/build/armhf/tools/lldb/test/SymbolFile/DWARF/Output/dwarf5-debug_line-file-index.s.tmp' (x86_64). (lldb) image lookup -f hello.c -l 1 PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace. Stack dump: 0. Program arguments: /home/omair.javaid/work/lldb/build/armhf/bin/lldb --no-lldbinit -S /home/omair.javaid/work/lldb/build/armhf/tools/lldb/test/Shell/lit-lldb-init /home/omair.javaid/work/lldb/build/armhf/tools/lldb/test/SymbolFile/DWARF/Output/dwarf5-debug_line-file-index.s.tmp -o "image lookup -f hello.c -l 1" Segmentation fault (core dumped)
Created attachment 24674 [details] coredump thread back trace
I believe 10d54e2f8d will fix this. Or, more like, work around the problem, since the invalid input should not cause a crash. Lets not close this bug until we understand what's happening there...
The underlying issue fixed by 2ecf928153fc56dcb6bb0bd910584eac86bc23bd.
OK for 12.0.1 backport.
The fix does not apply cleanly, could someone backport this and push a branch to their local github fork?