Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SCP: Ctrl-C/Ctrl-F does not work as intended for debugger #309

Open
al20878 opened this issue Oct 10, 2023 · 0 comments
Open

SCP: Ctrl-C/Ctrl-F does not work as intended for debugger #309

al20878 opened this issue Oct 10, 2023 · 0 comments

Comments

@al20878
Copy link
Contributor

al20878 commented Oct 10, 2023

  • Context

I definitely remember that it used to work at some time in the past. When the simulator (I use PDP11) is built with "DEBUG=1", started under "gdb", and then let run (with the "r" command), <Ctrl/C> was delivered to the software running under the simulator, and <Ctrl/F> would stop simh and get the gdb prompt.

Running it today, <Ctrl/C> gets delivered as SIGINT, causing the gdb prompt outright. OTOH, <Ctrl/F> also seems to deliver SIGINT, and get the gdb prompt, BUT here's the difference:

using the "continue" (c) command in gdb, continues the simulation in the first case; and in the second case, simh bails out to the sim> prompt (as if <Ctrl/E> was pressed). And there seems to be no way for the simulated software to get to read <Ctrl/C>.

Something has changed in the behavior. I wonder could it be caused by the readline drop-in replacement?

  • how you built the simulator or that you're using prebuilt binaries

make DEBUG=1 pdp11

  • the expected behavior and the actual behavior

I suppose it should work as it states:

sim> b rl
%SIM-INFO: SIGINT will be delivered to your debugger when the ^F character is entered
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant