Qt 6.11 is out! See what's new in the release
blog
Could not launch debugger on Mac
-
Got this whenever I try to launch the debugger:
Starting debugger "QmlCppEngine" for ABI "x86-macos-generic-mach_o-64bit"... dStart parameters: 'viewer' mode: 1 dABI: x86-macos-generic-mach_o-64bit dLanguages: any c++ qml dExecutable: /Users/uranusjr/Documents/programming/cpp/pepsi/build/qt5/debug/bin/pepsiviewer.app/Contents/MacOS/pepsiviewer -qmljsdebugger=port:52715,block,services:DebugMessages,QmlDebugger,V8Debugger,QmlInspector dDirectory: /Users/uranusjr/Documents/programming/cpp/pepsi/build/qt5/debug/bin/pepsiviewer.app/Contents/MacOS dDebugger: /Applications/Xcode.app/Contents/Developer/usr/bin/lldb dProject: /Users/uranusjr/Documents/programming/cpp/pepsi/pepsiAddtional Search Directories: dQML server: 127.0.0.1:52715 dRemote: :0 dSysroot: dDebug Source Location: dDebugger settings: dShowQObjectNames: false (default: false) dShowQtNamespace: true (default: true) dAutoDerefPointers: true (default: true) dSortStructMembers: true (default: true) dAutoEnrichParameters: true (default: true) dWatchdogTimeout: 20 (default: 20) dTargetAsync: false (default: false) dUseDynamicType: true (default: true) dMultiInferior: false (default: false) dWarnOnReleaseBuilds: true (default: true) dIdentifyDebugInfoPackages: false (default: false) dIntelFlavor: false (default: false) dBreakpointCorrection: true (default: true) dCDB_Console: false (default: false) dLoadGdbInit: true (default: true) dIgnoreFirstChanceAccessViolation: false (default: false) dAttemptQuickStart: false (default: false) dLoadGdbDumpers2: false (default: false) dGdbPostAttachCommands: (default: ) dGdbStartupCommands: (default: ) dExtraDumperFile: (default: ) dAlwaysAdjustColumnWidths: true (default: true) dAdditionalArguments: (default: ) dGdbCustomDumperCommands: (default: ) dSourcePaths: (default: ) dSymbolPaths: (default: ) dBreakOnCrtDbgReport: false (default: false) dBreakEvent: (default: ) dUseToolTips: true (default: true) dShowThreadNames: false (default: false) dUseToolTipsInBreakpointsView: false (default: false) dUseToolTipsInLocalsView: false (default: false) dUseAddressInBreakpointsView: false (default: false) dUseToolTipsInBreakpointsView: false (default: true) *** dUseAddressInStackView: false (default: false) dCloseMemoryBuffersOnExit: true (default: true) dCloseBuffersOnExit: false (default: false) dBreakpointsFullPath: false (default: false) dSwitchModeOnExit: true (default: false) *** dStationaryEditorWhileStepping: false (default: false) dRaiseOnInterrupt: false (default: true) *** dUseCodeModel: true (default: true) dUseDebuggingHelper: true (default: true) dUseAlternatingRowColours: true (default: false) *** dUseMessageBoxForSignals: true (default: true) dFontSizeFollowsEditor: true (default: false) *** dAutoQuit: false (default: false) dLogTimeStamps: false (default: false) dQmlInspector.ShowAppOnTop: false (default: false) dSelectedPluginBreakpointsPattern: .* (default: .*) dNoPluginBreakpoints: false (default: false) dBreakOnCatch: false (default: false) dBreakOnThrow: false (default: false) dBreakOnFatal: true (default: false) *** dBreakOnWarning: false (default: false) dShowQmlObjectTree: true (default: true) dBreakOnAbort: false (default: false) dDisplayStringLimit: 100 (default: 100) dMaximalStringLength: 10000 (default: 10000) dEnableReverseDebugging: false (default: false) dSkipKnownFrames: false (default: false) dAllPluginBreakpoints: true (default: true) dAdjustBreakpointLocations: true (default: true) dSelectedPluginBreakpoints: false (default: false) dMaximalStackDepth: 20 (default: 20) dShowStandardNamespace: true (default: true) dState changed from DebuggerNotReady(0) to EngineSetupRequested(1) [master] dQUEUE: SETUP ENGINE dCALL: SETUP ENGINE dState changed from DebuggerNotReady(0) to EngineSetupRequested(1) dQUEUE: SETUP ENGINE dState changed from DebuggerNotReady(0) to EngineSetupRequested(1) dQUEUE: SETUP ENGINE dCALL: SETUP ENGINE dNOTE: ENGINE SETUP OK dState changed from EngineSetupRequested(1) to EngineSetupOk(3) dQUEUE: SETUP INFERIOR dCALL: SETUP ENGINE dSTARTING LLDB: /Applications/Xcode.app/Contents/Developer/usr/bin/lldb eERROR: Lldb stderr: Traceback (most recent call last): e File "<string>", line 1, in <module> eERROR: Lldb stderr: File "/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources/Python/lldb/__init__.py", line 98, in <module> e import six eImportError: No module named six >(lldb) sc print('@\nlldbstartupok@\n') eERROR: Lldb stderr: Traceback (most recent call last): e File "<string>", line 1, in <module> eNameError: name 'run_one_line' is not defined eTraceback (most recent call last): e File "<string>", line 1, in <module> eNameError: name 'run_one_line' is not defined eTraceback (most recent call last): e File "<string>", line 1, in <module> eNameError: name 'run_one_line' is not defined eTraceback (most recent call last): e File "<string>", line 1, in <module> eNameError: name 'run_one_line' is not defined eTraceback (most recent call last): e File "<string>", line 1, in <module> eNameError: name 'run_one_line' is not defined eTraceback (most recent call last): e File "<string>", line 1, in <module> eNameError: name 'run_one_line' is not defined eerror: python failed attempting to evaluate 'print('@\nlldbstartupok@\n')'The debugger used to work, but I haven’t used Qt Creator for a while. Maybe it is an Xcode upgrade that broke this, but I am not sure. From the error log it seems that my Python environment is messed up. Does anyone have an idea how I could fix this?
-
Managed to hack the import path by adding
import sys sys.path.append('/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python')in
/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources/Python/lldb/__init__.py, before importing six. This messes up the Python environment more, but at least I can launch the debugger now.Still hoping there could be a “real” solution. I can launch both
/usr/bin/lldband/Applications/Xcode.app/Contents/Developer/usr/bin/lldbwithout a problem in the console, so maybe this is related to how Qt Creator launches the debugger subprocess? -
Hi,
Can you check the latest version of Qt Creator ? IIRC it should 4.0.3
If you still have the same problem without your "hack" you should take a look at the bug report system to see if its something known.
