Breakpoints from temporary files created for macros accumulate and are not deleted

[Mideks]

When a command with a macro is used, a temporary file is created in debugging mode, into which the arguments of the macro are inserted. Breakpoints from the original file are copied there. But they don't go away, and you have to delete them manually.

During debugging:

The next time you run the debugger, they also remain.:

[Papierkorb2292]

So the breakpoint mirroring is kind of brittle, but I thought I had ironed out most bugs like this. I just tried setting a breakpoint in a function with macros, pausing at it, and then continuing, and the copied breakpoint was then removed as it should. Can you give more details on how to reproduce this? Is your datapack maybe available online so I could directly test with that?

Edit: Is your function using recursion? I don't think I ever tested the breakpoints with recursion...

[Mideks]

Yes, my function uses recursion.

Unfortunately, my datapack is not publicly available, but I tried to separate the recursion function from everything else. You can try it.

Run something like this:

execute as @p run function spear_game:arena/grid_check/start {command:"setblock ~ ~ ~ stone"}

dp_recursion.zip

[Papierkorb2292]

Thanks, that definitely isn't working right. I noticed the copied breakpoints are not removed when the original breakpoint is removed and the debugger seems to be really slow. But I can't reliably reproduce the issue that the copied breakpoints stay even after exiting the function, do you have more detailed steps that lead to this problem?

[Papierkorb2292]

Oh, I think I get it, did you stop the debugger while it was paused? It seems like I forgot to remove the breakpoints in that situation

[Mideks]

Hmm, most likely yes, I interrupted the debugger before completing the full function execution. (that would be too long, lol)

I also noticed that such a stop could possibly cause minecraft to freeze, and it would stop accepting any commands. But I'm not sure about that. I will issue a separate issue if this happens again.

[Papierkorb2292]

Alright, I'll work on a fix for the breakpoints and then close this issue with the release of the next version

I think someone else told me a while ago they also had Minecraft freeze after stopping the debugger during a pause, but it only happened once and then neither of us could reproduce it again... So if you happen to stumble upon a way to make that happen that would be nice. But also, if that does happen, it should be possible to rejoin the world/server to make it continue.

[Mideks]

When this happened, after hanging up, I tried to rejoin the world, but it froze at the moment of saving. I had to kill minecraft and restart it...
But after that, everything worked as it should, yes