VICE not launching or attaching on debug
torokze opened this issue · 11 comments
Hi,
I have this debugger issue with VICE 3.7-win64. Neither attach nor launch works.
The internal debugger works just fine. The VICE works. There are no multiple instances at the same time.
I'm using Windows 11, VSCode 1.77.3, VS64 2.2.1
attach.vscode-app-1682831715579.log
launch.vscode-app-1682831806691.log
vice.log
You could try the following:
- manually launch vice
- make sure the "Binary Remote Monitor" is enabled on port 6502
- make sure the "Remote Monitor" is NOT using port 6502
- now "attach" your program to vice (using port 6502)
Does that connect and work? If yes, save your settings and try the automated way again.
I've tried these:
- x64sc.exe -binarymonitor -binarymonitoraddress ip4://127.0.0.1:6502 -autostartprgmode 1 -remotemonitoraddress ip4://127.0.0.1:6510
- x64sc.exe -binarymonitor -binarymonitoraddress ip4://127.0.0.1:6502 -autostartprgmode 1 +remotemonitor
launch.json entry:
{ "type": "vice", "request": "attach", "name": "Attach Vice", "hostname": "localhost", "port": 6502, "preLaunchTask": "${defaultBuildTask}" }
The emulator starts but as soon as I hit F5 (attach vice) it quits in both cases.
"Quits in both cases" means: the debugging session stops / detaches unexpectedly, but the VICE process keeps going?
Another Idea: When installing VICE on Windows, there's the antivirus trying to shield your computer. Could you try to manually start to see if VICE is working as expected?
VICE 3.7 SDL
The vice process quits completely.
I'll try the GTK version ASAP.
The GTK version works as expected. Thanks.
Hmmm. I'll check with the SDL version later today!
I can reproduce the VICE-SDL crash on windows, but cannot explain. The only thing I could improve was the handling of the crash and the resulting ECONNRESET socket failure.
Btw. it works seamlessly on Linux x64 with the SDL version of VICE. Seems to be a Win64/SDL/VICE bug.