feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Debugger: Print a message when returning early from __lldb_init_module

Browse Source 
It helps figuring out why the dumper is not being initialized when
it's called by the Qt Core lldb debugger script.

Task-number: QTCREATORBUG-31769
Change-Id: If268a8ee9aadf5ccb9e0a995c317bcd250f64958
Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
Alexandru Croitor
2024-10-09 17:04:10 +02:00
parent 2d615d453e
commit 17b1cf0544
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
share/qtcreator/debugger/lldbbridge.py
View File

@@ -2530,7 +2530,7 @@ def ensure_gdbmiparser():
def __lldb_init_module(debugger, internal_dict): def __lldb_init_module(debugger, internal_dict):
# Module is being imported in an LLDB session # Module is being imported in an LLDB session
if 'QT_CREATOR_LLDB_PROCESS' in os.environ: if 'QT_CREATOR_LLDB_PROCESS' in os.environ:
# Let Qt Creator take care of its own dumper debug("Returning early, letting Qt Creator take care of its own dumper", debugger)
return return
debug("Initializing module with", debugger) debug("Initializing module with", debugger)