search

CaptainJiNX / vscode-kickass-c64

Visual Studio Code extension for C64 coding with Kick Assembler
MIT License
19 stars 4 forks source link

Automatically move breakpoints into c64debugger #1

Closed gitsoft closed 6 years ago

gitsoft commented 6 years ago

Automatically move breakpoints into c64debugger

TLDR; KickAss exports breakpoints to a separate file so that VICE can use them. C64Debugger supports a breakpoint file, but it has another format then VICE. The code added in the pull request simply extract the breakpoints from the VICE file and create a separate file for C64Debugger when KickAss completed a build (Build And Debug Startup).

Nitty gritty + blah blah

KickAss -vicesymbols output look like this. It contains labels and breakpoints.

al C:837 .WaitForRasterLine al C:811 .mainloop al C:810 .start al C:80b .upstartEnd break 810 break 816

To reuse this exported information I simply loop through the exported VICE symbol file and add any breakpoint line to a separate file. The result would look like this

break 810 break 816

Finally that new file (with extension .breakpoints) is passed with argument -breakpoints to the Slajerek's C64debugger.

Developed and tested successfully using

Verification in VS Code Add a breakpoint to a asm file using the usual format

.break

Save. Do a Build And Debug Startup Open the .breakpoints in the binfolder to verify the entry exists

Verification in C64Debugger After starting Build And Debug Startup, open the breakpoint window in C64Debugger using CMD + B (CTRL + B on Windows). The breakpoint will be listed there.

CaptainJiNX commented 6 years ago

Awesome Bernie. I think you forgot to install prettier though, but I'll merge this and reformat it.