BUG - Control-C/Stop command break into debugger

For me, this only seems to happen the first time after the initial side-load. So, if you exit the channel and re-launch it as part of your side-loading procedure, you should be able to break into it from that point on without it exiting.

Yeah, it is frustrating when trying to do a quick debug of some code. Sometimes it works.

THIS!
I just lost an hour of work because of this dev.environment bug and am fuming.
Can someone Roku* have a look please - is this logged as a bug? What are expectations of it getting fixed?

And here is how i got screwed by it today: i have been running my simulation on Roku and after about an hour noticed there are some boundary issues/artefacts. Aha - now if i look at the raw data i will know what's wrong - just have to interrupt it and print an array - so i press ctrl-C at iteration #52063 and... i am fracked, backtrace prints but program exits and there is nothing i can do but start from the beginning. :cry:

I think everyone that develops for B/S know the behavior and we kind of go along with it since "you just have to restart your program once more". And once more. And once more. What is interesting is that it happens EVERY OTHER TIME, as a metronome - tick-tock, tick-tock. Meaning if you interrupt program at time N and console works, next start N+1 a break will exit to main menu, then at N+1 will break into console and so on. It feels like something reliable that easily can be tracked down and fixed, some boolean kind of condition.

Any other developers tormented by this, can you add your voice (and horror stories) here, hopefully to get some attention to the issue?

This has been tormenting me too. Every other time exactly the channel exits the debugger. I'm now in the habit of running the channel twice whenever I want to debug something, the first time knowing it will exit without letting me debug, the second time is when I get to do my actual debugging. It doesn't seem to be related to whether I've just side-loaded the channel or whether I've run it from the home screen.

Yeah, it's ridiculous that this behavior still exists after all these years, but I don't see the same behavior as you do. For me, it seems to almost always fail the first time I hit Ctrl-C (or my code hits a stop), but after that it seems to work ok. I've gotten into the habit of starting my development channel and hitting Ctrl-C immediately and then restarting the channel and repeating until Ctrl-C works properly. After that, I can't say that I have any problems, but I haven't been doing a whole lot of development lately.

-JT