[Bug 263387] devel/qtcreator: debugging completely broken
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 18 Apr 2022 07:19:16 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263387 Bug ID: 263387 Summary: devel/qtcreator: debugging completely broken Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: kde@FreeBSD.org Reporter: ivan@drm.su Assignee: kde@FreeBSD.org Flags: maintainer-feedback?(kde@FreeBSD.org) Well, something broke debugging feature after recent update on my system. 13.1-RC3 Tried qtcreator 5.0.3_1 and 6.0.2 with lldb13 and lldb14. No luck. In the debugger console I have this: >(lldb) script sys.path.insert(1, '/usr/local/share/qtcreator/debugger/') >(lldb) script from lldbbridge import * >(lldb) script theDumper.loadDumpers({"token":13}) >(lldb) script theDumper.executeDebuggerCommand({"command":"settings append target.source-map /home/qt/work/qt /usr/local/include/../Src","token":14}) eERROR: Lldb stderr: 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') eerror: lua failed attempting to evaluate 'from lldbbridge import *': [string "buffer"]:1: syntax error near 'lldbbridge' eerror: lua failed attempting to evaluate 'theDumper.loadDumpers({"token":13})': [string "buffer"]:1: '}' expected near ':' eerror: lua failed attempting to evaluate 'theDumper.executeDebuggerCommand({"command":"settings append target.source-map /home/qt/work/qt /usr/local/include/../Src","token":14})': [string "buffer"]:1: '}' expected near ':' ❯ ls /usr/local/share/qtcreator/debugger/ LICENSE.GPL3-EXCEPT creatortypes.py lldbbridge.py personaltypes.py utils.py README.txt dumper.py misctypes.py qttypes.py boosttypes.py gdbbridge.py opencvtypes.py setup.cfg cdbbridge.py gdbtracepoint.py pdbbridge.py stdtypes.py It looks like lldb tries to load python script with lua interpreter. Any ideas how to fix it? Waiting for v7.0.0 binary packages to try with. -- You are receiving this mail because: You are the assignee for the bug.