search

hth313 / Calypsi-tool-chains

Overview of the Calypsi tool chain and open source support packages
16 stars 0 forks source link

VSCode debugginging error #9

Closed Papakura closed 1 year ago

Papakura commented 1 year ago

When trying to debug with VSCode I the following error image

The debugger seems not to recognize "solib-serach-path" gdb command VSCode

Version: 1.74.1 (user setup) Commit: 1ad8d514439d5077d2b0b7ee64d2ce82a9308e5a Date: 2022-12-14T10:30:51.966Z Electron: 19.1.8 Chromium: 102.0.5005.167 Node.js: 16.14.2 V8: 10.2.154.15-electron.0 OS: Windows_NT x64 10.0.19045 Sandboxed: No

C/C++ for Visual Studio Code V1.13.8 The one mentioned in documentation returns 404

Calypsi debugger for 65816 version 3.6.10

hth313 commented 1 year ago

You need to remove that from the command line in the launch configuration. There is no need for setting a shared library path, it has no meaning to db65816. The user guide should contain an example you can use as a starting point.

Papakura commented 1 year ago

The launch.json does not include anything about shared library. It must the cpptoools debugger host that is calling with that command { // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "name": "Launch", "type": "cppdbg", "request": "launch", "program": "${workspaceFolder}/main.elf", "args": ["--logging-enable"], "stopAtEntry": false, "cwd": "${workspaceFolder}", "environment": [], "externalConsole": false, "MIMode": "lldb", "miDebuggerPath": "C:/Program Files (x86)/Calypsi-65816/bin/db65816.exe", "symbolLoadInfo": { "loadAll": false, "exceptionList": "" } }

]

}

Papakura commented 1 year ago

I get the same thing with the launch.json from the user guide

hth313 commented 1 year ago

Then they most likely changed the cpp-tools plug-in. You may file a question in that project https://github.com/microsoft/vscode-cpptools

I may dig into it in the coming days, but as you did not configure it that way, then it is most certainly something they do on their end and the question is if it can be configured not to do it.