From 17b1cf054436f048d93b11a1bab82eedf065e92f Mon Sep 17 00:00:00 2001 From: Alexandru Croitor Date: Wed, 9 Oct 2024 17:04:10 +0200 Subject: [PATCH] Debugger: Print a message when returning early from __lldb_init_module 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 --- share/qtcreator/debugger/lldbbridge.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/share/qtcreator/debugger/lldbbridge.py b/share/qtcreator/debugger/lldbbridge.py index 3f7ec792a61..2ae1cb29bfe 100644 --- a/share/qtcreator/debugger/lldbbridge.py +++ b/share/qtcreator/debugger/lldbbridge.py @@ -2530,7 +2530,7 @@ def ensure_gdbmiparser(): def __lldb_init_module(debugger, internal_dict): # Module is being imported in an LLDB session 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 debug("Initializing module with", debugger)