Closed 64kramsystem closed 2 years ago
(I've reported this in https://github.com/rosc77/vs64/issues/27, however, I think it's worth separating the two issues)
When the debugger/emulator are misconfigured, the extension starts the debug session without actually notifying that something went wrong.
Swallowing the error makes it difficult to diagnose problems, since no output is proceduced.
My fault. This is due to my misunderstanding that the standard debug task (F5) would launch a full c64 debugging, while it actually launches the 6502-only emulator.
(I've reported this in https://github.com/rosc77/vs64/issues/27, however, I think it's worth separating the two issues)
When the debugger/emulator are misconfigured, the extension starts the debug session without actually notifying that something went wrong.
Swallowing the error makes it difficult to diagnose problems, since no output is proceduced.