https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263387
Florian Walpen <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Florian Walpen <[email protected]> --- Looks like these commands are actually run _inside_ lldb, with the relevant qtcreator code in src/plugins/debugger/lldb/lldbengine.cpp: > executeCommand("script sys.path.insert(1, '" + > rp.dumperPath.path().toLocal8Bit() + "')"); > // This triggers reportState("enginesetupok") or "enginesetupfailed": > executeCommand("script from lldbbridge import *"); lldb gained support for lua scripting in recent versions, even though python is probably still default. There is a CLI argument (-l or --script-language) to choose the language, but I don't see it used in qtcreator sources. @Ivan: Can you double check in the debugger logs that qtcreator uses lldb13 or lldb14 from ports, something like: > STARTING LLDB: /usr/local/bin/lldb14 At least on 13.0-RELEASE lldb in base defaults to lua scripts... > ~> /usr/bin/lldb > (lldb) script sys.path.insert(1, '/usr/local/share/qtcreator/debugger/') > error: lua failed attempting to evaluate 'sys.path.insert(1, > '/usr/local/share/qtcreator/debugger/')': [string "buffer"]:1: attempt to > index a nil value (global 'sys') ...whereas lldb13 from ports defaults to python: > ~> /usr/local/bin/lldb13 > (lldb) script sys.path.insert(1, '/usr/local/share/qtcreator/debugger/') > (lldb) script sys.path > ['/usr/local/llvm13/lib', '/usr/local/share/qtcreator/debugger/', > '/usr/local/llvm13/lib/python3.8/site-packages', > '/usr/local/lib/python38.zip', '/usr/local/lib/python3.8', > '/usr/local/lib/python3.8/lib-dynload', > '/usr/local/lib/python3.8/site-packages', '.'] -- You are receiving this mail because: You are the assignee for the bug.
