According to the built-in help, pressing Ctrl+c should suspend the current program and display the “suspended>” prompt, but for me it does nothing. Pressing Ctrl+d to quit works with no problems. I’ve tested in xterm to try and remove any potential issues with the terminal but I get the same result.
Does suspending the program work for anyone else?
> @help
Dialog Interactive Debugger (dgdebug) version 0m/03
...
You can press ^C to suspend the program while it is running. At the the "suspended>" prompt, you can run queries and debugging commands. A blank
line of input resumes the program.
...
Yes, and then “resume” with (undo), but I guess that needing to modify the game state in order to suspend it might defeat the purpose of wanting to suspend it.
i guess i never thought to suspend the debugger since debugging commands and queries still work while it’s running. is there something that you CAN’T do from within the debugger that you CAN do while suspended?
I believe Ctrl-C specifically works while the debugger is executing code, not while it’s waiting for input. The main reason to use it is when you have reams of (trace on) output printing, and you want to stop it so you can (trace off).
I am trying to finish an attempt at Emacs integration with the debugger and wasn’t sure exactly what would happen if that signal ever gets sent. It looks like you do need it if you end up getting flooded with [more] prompts (probably caused by the trace output).