dimitripilot3 / nds_vscode_template Goto Github PK

VSCode supports "launch" and "attach" configurations. At this time, the only configuration is (gdb) Launch which - in my eyes - is really just supposed to be an attach configuration.

I'm new to this, but feel it'd make more sense to have two launch configs (one for desmume stable release, one for dev+ with a gdb interface) and one attach config. And remove the gdb-debug helper task, if possible.

Currently, when debugging, we use a dev+ build of DeSmuME 0.9.11 (an older release) to attach gdb to, which offers a --cpu-mode=(0|1) option letting us choose between the CPU interpreter and the JIT. We need the interpreter, as most of the gdb stuff doesn't work with the JIT.

After commit TASEmulators/desmume@3785435, --cpu-mode=(0|1) was later replaced with --jit-enable which doesn't accept an option argument, leaving us without a stable-0.9.13-viable alternative to --cpu-mode=0.

This may be an issue in the event that an user starts editing tasks.json to change the README-suggested desmume path from DeSmuME_0.9.11_x86_dev+ to that of a newer dev+ executable. For instance, running any of the following:

DeSmuME_0.9.13_x64.exe --cpu-mode=0 <path to NDS executable>
DeSmuME_0.9.13_x64.exe --jit-enable=0 <path to NDS executable>

will exit on startup because the first command argument is not recognized as an option; meanwhile --jit-enable is recognized as such.

Possible workarounds

• launch desmume, untick the Emulation Settings -> Use dynamic recompiler option in the GUI, then close desmume;
• or, edit desmume.ini on windows, which could be done programmatically via tasks.json and using sed/awk tools;
• or, launch desmume with the cwd (working directory) set to a directory located in the NDS project and place our own, read-only desmume.ini file there