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

cmake: emu: qemu: return to ctrl-c #79131

Open
fgrandel opened this issue Sep 27, 2024 · 0 comments · May be fixed by #79132
Open

cmake: emu: qemu: return to ctrl-c #79131

fgrandel opened this issue Sep 27, 2024 · 0 comments · May be fixed by #79132
Labels
bug The issue is a bug, or the PR is fixing a bug

Comments

@fgrandel
Copy link
Contributor

Describe the bug

Ctrl-C doesn't work after stopping QEMU x86 with IEEE 802.15.4 monitor. The intr signal is mapped to Ctrl-D.

PR follows.

Expected behavior

stty intr should be mapped to Ctrl-C.

Impact

very minor

Logs and console output

n/a

Environment (please complete the following information):

Linux only

Additional context

I recently remapped Ctrl-C to Ctrl-D when QEMU has the IEEE 802.15.4 monitor running in the background, so that users won't inadvertently press Ctrl-C to stop the VM and keep the monitor running. This works nicely but I forgot to also map back to Ctrl-C after shutting down the VM.

@fgrandel fgrandel added the bug The issue is a bug, or the PR is fixing a bug label Sep 27, 2024
fgrandel added a commit to fgrandel/zephyr that referenced this issue Sep 27, 2024
To avoid killing the QEMU process w/o also ending the 802.15.4
monitoring tool, we reassign the terminal's interrupt shortcut from ^C
to ^D. This change resets the shortcut to ^C after ending the QEMU
session.

Fixes zephyrproject-rtos#79131

Signed-off-by: Florian Grandel <[email protected]>
@fgrandel fgrandel linked a pull request Sep 27, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant