Closed 64kramsystem closed 2 years ago
I've had a look at the developer tools, and this is the output of a sample run (with breakpoint trigger):
console.ts:137 [Extension Host] dispatch request: initialize({"clientID":"vscode","clientName":"Visual Studio Code","adapterID":"asm","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en-us","supportsProgressReporting":true,"supportsInvalidatedEvent":true,"supportsMemoryReferences":true})
console.ts:137 [Extension Host] dispatch request: launch({"type":"asm","request":"launch","name":"Launch Program","binary":"/home/saverio/code/pl64/.cache/hello.prg","__configurationTarget":5,"debugServer":40405,"__sessionId":"d3d005c6-0e9d-497c-ba9a-9c18743f91a9"})
console.ts:137 [Extension Host] send event: initialized({"seq":0,"type":"event","event":"initialized"})
console.ts:137 [Extension Host] dispatch request: setBreakpoints({"source":{"name":"hello.asm","path":"/home/saverio/code/pl64/hello.asm"},"lines":[9,14,15],"breakpoints":[{"line":9},{"line":14},{"line":15}],"sourceModified":false})
console.ts:137 [Extension Host] dispatch request: configurationDone(undefined)
console.ts:137 [Extension Host] emulator stopped...
console.ts:137 [Extension Host] send event: stopped({"seq":0,"type":"event","event":"stopped","body":{"reason":"breakpoint","threadId":1,"description":"Paused on breakpoint"}})
console.ts:137 [Extension Host] dispatch request: threads(undefined)
console.ts:137 [Extension Host] dispatch request: threads(undefined)
console.ts:137 [Extension Host] dispatch request: stackTrace({"threadId":1,"startFrame":0,"levels":20})
console.ts:137 [Extension Host] dispatch request: stackTrace({"threadId":1,"startFrame":0,"levels":20})
console.ts:137 [Extension Host] dispatch request: scopes({"frameId":1})
console.ts:137 [Extension Host] dispatch request: variables({"variablesReference":1})
It was run with "c64.debuggerEnabled": false
; when setting it as true, the log is essentially the same.
Closing, same misunderstanding as here.
Hello!
I'm attempting to debug a program, but, while the debugger actually runs, there is no visual output.
A few details:
I think that the problem is that the extension doesn't notify the user if anything goes wrong. If I modify the debugger/emulator paths to be incorrect, the debug session still starts without displaying any error.
If the extension didn't swallow the error, and stop and display it instead, it would be very useful to diagnose what's the actual problem.