vscode-kcide
vscode-kcide copied to clipboard
floooh
breakpoint is deactivated in the asm file subfolder
There is an annoying bug in the debugger that it deactivates the breakpoint in the files that are in the subfolders
As you can see in the picture, by running the debugger, the breakpoint is deactivated for the reason "unverified breakpoint".
Maybe it is my fault and something is missing in my configuration file
It's most like a bug related to path handling, there are some annoying differences between UNIX-like systems and Windows, and also between desktop and web which need special case handling.
What operating system are you on?
...it works on macOS at least:
...will check on Windows next.
...hmm it also works on Windows.
Can you provide more info which would help me to reproduce the problem?
Sorry for late answer, I'm using Windows 11.
I was thinking that the issue might be linked to OneDrive, but even in hard disk, I have the same issue
I found also another problem, the breakpoint doesn't work in the main program when org is 0000h.
Ah ok, getting closer.
I can at least reproduce the "breakpoints on address 0 are not working" on the CPC emulator, but not on the KC85/4 emulator (I did test this case, because I thought it might be related to https://github.com/floooh/vscode-kcide/issues/7, but not on the CPC emulator).
As far as I can see, this is unrelated to "source code is in a subdirectory" though, at least I cannot reproduce this case, unless the breakpoint in code pulled in from a subdirectory is located at address 0.
I'll check why breakpoints at address zero don't work together with the CPC emulator....
Hmm, no it's not as simple as that... this works for instance on the CPC emulator:
...however, after running the programm the emulator gets into an invalid state, because the memory page at address 0 isn't switched back to the 'shadow ram' state. The emulator needs to be rebooted before starting again...