From: Launchpad Bug Tracker <1031920@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1031920] Re: Linux user gdbserver does not respond to remote `Ctrl-C' interrupts
Date: Sun, 02 Apr 2017 04:17:25 -0000 [thread overview]
Message-ID: <20170402041725.11031.61633.malone@loganberry.canonical.com> (raw)
In-Reply-To: 20120801202321.9879.66283.malonedeb@wampee.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1031920
Title:
Linux user gdbserver does not respond to remote `Ctrl-C' interrupts
Status in QEMU:
Expired
Bug description:
The bug was reproduced in a recent mainline build for ARM Linux by
starting emulation with a gdbserver:
$ qemu-arm -g 1234 a.out
and then connecting from gdb:
(gdb) target remote :1234
Remote debugging using :1234
[New Remote target]
[Switching to Remote target]
0x00008ba8 in _start ()
(gdb) b main
Breakpoint 1 at 0x8cb0: file hello.c, line 5.
(gdb) cont
Continuing.
Breakpoint 1, main (argc=1, argv=0xf6fff24c) at hello.c:5
5 int n = 0;
(gdb) l
1 #include <stdio.h>
2
3 int main (int argc, char **argv)
4 {
5 int n = 0;
6
7 for (;;) {
8 printf ("Hello, World!\n");
9 sleep (5);
10 }
(gdb) cont
Continuing.
^C^CInterrupted while waiting for the program.
Give up (and stop debugging it)? (y or n) y
Notice that the `Ctrl-C' interrupts are ignored.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1031920/+subscriptions
prev parent reply other threads:[~2017-04-02 4:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 20:23 [Qemu-devel] [Bug 1031920] [NEW] Linux user gdbserver does not respond to remote `Ctrl-C' interrupts Meador Inge
2015-10-14 15:27 ` [Qemu-devel] [Bug 1031920] " thierry bultel
2017-01-31 9:14 ` Thomas Huth
2017-04-02 4:17 ` Launchpad Bug Tracker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170402041725.11031.61633.malone@loganberry.canonical.com \
--to=1031920@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.