-
-
Notifications
You must be signed in to change notification settings - Fork 11
Does not run correcly on it own, sometimes... Most of the time i need to go to the DEBUG CONSOLE to using the targert and continue command #28
Description
Update: Thought is was working great, and then it stopped w/o any changes to anything I could think of. The OUTPUT screen is virtually useless. Why doesn't the author make this open source so it can be fixed?
My setup is a bit complex. Development computer is a current macbook, using VScode to connect to a docker image to do the cross compile for a luckpro pico ultra. I don't have any issues building, copying, and running the code on the pico using scp and just ssh'ing into the target and executing the app.
Here is my launch.json
{
"name": "remote gdb",
"type": "by-gdb",
"request": "launch",
"stopAtEntry": true,
"debuggerPath": "gdb-multiarch",
"program": "./linuxbuild/server",
"cwd": "${workspaceRoot}",
"remote": {
"enabled": true,
"address": "192.168.1.168:1234",
"mode": "extended-remote",
"execfile": "server"
}
}
On the target, I execute target remote --multi :1234 ./server
When I press the run button (arrow), a blue indicator goes back and forth, but nothing happens. So out of a sheer accident, I went the VSCodes DEBUG CONSOLE tab, then typed target extended-remote 192.168.1.168:1235, following by continue, and the app started running and stopped at the first breakpoint. Everything seems to work fine except for the extra steps.
Oddly, all the breakpoints are being set, and that appears to happen before I start manually typing commands.
The messages on the OUTPUT tab are not verbose enough to understand what is going wrong.
Please help.