What is killing LLDB's Debug Server on specific binaries' crashes?

Subprojects LLDB
1

When I attempt to debug an ANR, I always see “debugserver died with an exit status of 0x00000000” [1] after a consistent amount of seconds:

RokeJulianLockhart@Beedell:~$ lldb -- okular /home/RokeJulianLockhart/Downloads/official-cpe-dictionary_v2.3.xml (lldb) target create "okular" Current executable set to '/usr/bin/okular' (x86_64). (lldb) settings set -- target.run-args "/home/RokeJulianLockhart/Downloads/official-cpe-dictionary_v2.3.xml" (lldb) run Process 78758 launched: '/usr/bin/okular' (x86_64) warning: (x86_64) /usr/lib64/dri-freeworld/libgallium-25.1.4.so unsupported DW_FORM values: 0x1f20 0x1f21 kf.windowsystem: static int KX11Extras::currentDesktop() may only be used on X11 QObject::disconnect: wildcard call disconnects from destroyed signal of KToggleAction::mouse_toggle_annotate QObject::disconnect: wildcard call disconnects from destroyed signal of KToggleAction::show_leftpanel Process 78758 stopped * thread #1, name = 'okular', stop reason = signal SIGABRT frame #0: 0x00007ffff663634b libQt6Gui.so.6`QTextDocumentPrivate::insert_block(int, unsigned int, int, int, QTextUndoCommand::Operation, int) + 523 libQt6Gui.so.6`QTextDocumentPrivate::insert_block: -> 0x7ffff663634b <+523>: addl 0x10(%rcx), %edi 0x7ffff663634e <+526>: movl 0x8(%rcx), %ecx 0x7ffff6636351 <+529>: addl %edi, %esi 0x7ffff6636353 <+531>: testl %ecx, %ecx Process 78758 exited with status = -1 (0xffffffff) debugserver died with an exit status of 0x00000000

  1. stackoverflow.com/q/40048404 ↩︎

2

As I wrote that post, I realised that this might be caused by something more fundamental:

Perhaps, it’s outside the scope of this forum. Regardless, worth reporting? I imagine the LLDB developers want to do better than GDB’s, where possible.