The "emulicious-debugger" extension enables debugging with Emulicious in VS Code. This extension requires Emulicious (https://emulicious.net/). In Emulicious you need to have "Remote Debugging" enabled. This option can be found in Emulicious's Tools menu. For breakpoints to work you need a language extension for the language you are using.
For usage instructions see Usage.
Known issues are listed in Known Issues.
If you encounter any other issues please inform about them so they can be fixed.
If anything is unclear please also inform about that so the explenations can be improved.
The "emulicious-debugger" extension requires Visual Studio Code (VS Code) and Emulicious (https://emulicious.net/). In Emulicious you need to have "Remote Debugging" enabled. This option can be found in Emulicious's Tools menu. For breakpoints to work you need a language extension for the language you are using. If you are using C you can for example use the C language extension that is built into VS Code. For other languages you should be able to find a corresponding language extension in VS Code's Extension Marketplace. For example if you are developing for the Game Boy (Color) with RGBDS you can find Donald Hays's RGBDS Z80 extension.
Make sure that Emulicious is running and that "Remote Debugging" (in Emulicious's Tools menu) is enabled. After that is set up, you have multiple ways to start debugging with Emulicious:
When building your program, make sure that debug symbols get generated. For example, when building C code with SDCC you should pass the commandline flag
The "emulicious-debugger" extension enables source level debugging for assembler code and C code (SDCC).
Step through your own ASM source code.
Break on breakpoints in your ASM source code.
Keep an eye on your callstack.
Investigate registers annotated with symbols.
Investigate System State
Investigate system state.
Inspection on Hover
Inspect symbols on hover.
Evaluate expressions in debug console
Disassemble with Emulicious and step through the disassembly in VS Code.
Step through your C source code line by line, into procedures or out of them.
Break on breakpoints in your C source code.
Keep an eye on your C callstack.
C Local Variables
Keep track of your local variables.
C Inspection of Structured Type
Inspect your C arrays and structs via Watch expressions, on hover or via the debug console.
Trying to start a debug session without Emulicious running or without Remote Debugging enabled yields an error message saying that the connection was refused.
If you see this error make sure that you are running Emulicious and that Remote Debugging is enabled.
Added some missing keywords Improved some screenshots
Initial release of "emulicious-debugger"