teemperor added a comment. +1 to what Jonas said.
You can reproduce this by just adding an `abort();` call at the start of `CommandInterpreter::HandleCommand` and then for example like the `TestApropos.py` test. > If the LLDB process that this calls crashes, it shouldn't affect that. LLDB is loaded as a Python module *inside* the `Python` process, so Python and LLDB actually do share a process/signals (that's why when LLDB crashes in a Python test, you actually see the 'Python' process crashing. It's just a loaded shared library). Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D87637/new/ https://reviews.llvm.org/D87637 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
