[Qemu-devel] [Bug 1031920] [NEW] Linux user gdbserver does not respond to remote `Ctrl-C' interrupts

* [Qemu-devel] [Bug 1031920] [NEW] Linux user gdbserver does not respond to remote `Ctrl-C' interrupts
@ 2012-08-01 20:23 Meador Inge
  2015-10-14 15:27 ` [Qemu-devel] [Bug 1031920] " thierry bultel
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Meador Inge @ 2012-08-01 20:23 UTC (permalink / raw)
  To: qemu-devel

Public bug reported:

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.

** Affects: qemu
     Importance: Undecided
         Status: New

** Description changed:

- The bug was reproduce in a recent mainline build for ARM Linux by
+ 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	
+ 2
  3	int main (int argc, char **argv)
  4	{
  5	  int n = 0;
- 6	
+ 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.

-- 
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:
  New

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

^ permalink raw reply	[flat|nested] 4+ messages in thread