lldb crashes with print command on 12.2-RELEASE on booth i386 and amd64. 13-BETA prints 1 fine. % cat main.c int main() { } % cc -g main.c % lldb ./a.out (lldb) target create "./a.out" Current executable set to '/export/home/hiro/devel/mdb/hisqry/a.out' (i386). (lldb) b main Breakpoint 1: where = a.out`main + 5 at main.c:3:1, address = 0x00401765 (lldb) run Process 23215 launching Process 23215 launched: '/export/home/hiro/devel/mdb/hisqry/a.out' (i386) Process 23215 stopped * thread #1, name = 'a.out', stop reason = breakpoint 1.1 frame #0: 0x00401765 a.out`main at main.c:3:1 1 int main() 2 { -> 3 } (lldb) p 1 Program aborted due to an unhandled Error: Program aborted due to an unhandled Error: Error value was Success. (Note: Success values must still be checked prior to being destroyed). Stack dump: 0. Program arguments: lldb ./a.out 1. HandleCommand(command = "p 1") #0 0x03aa6a24 PrintStackTrace /usr/src/contrib/llvm-project/llvm/lib/Support/Unix/Signals.inc:564:13 #1 0x03aa6e2e /usr/src/contrib/llvm-project/llvm/lib/Support/Unix/Signals.inc:624:3 #2 0x03aa4aee RunSignalHandlers /usr/src/contrib/llvm-project/llvm/lib/Support/Signals.cpp:67:5 #3 0x03aa72f8 SignalHandler /usr/src/contrib/llvm-project/llvm/lib/Support/Unix/Signals.inc:0:3 #4 0x24667c49 handle_signal /usr/src/lib/libthr/thread/thr_sig.c:248:3 Abort
I can reproduce this, on 12.2-p4. Indeed later versions work fine, but it'll take some time to track down.
Ah, so this is actually a duplicate of bug 248745, which I fixed in base r364480. However, I forgot to MFC it in time for 12.2-RELEASE, so it was fixed after that for stable/12 in base r367228. Ed, do you think this would warrant an EN? I don't think lldb is completely unusable in 12.2-R, as other debugging commands appear to work OK, but this is still an annoying bug.
Thanks. I locally applied the patch and confirmed working okay on 12.2.
> Ed, do you think this would warrant an EN? This seems reasonable, we can include it when we have other EN/SAs to release.
^Triage: - Close DUPLICATE, re-opening duplicated issue for subsequent EN - Assign to committer that resolved (identified dupe) *** This bug has been marked as a duplicate of bug 248745 ***