[Bug remote/15297] CTRL-C with set debug remote often crashes GDB

["jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=15297

--- Comment #4 from Jan Kratochvil <jan.kratochvil at redhat dot com> ---
http://sourceware.org/gdb/wiki/TestingGDB#Testing_gdbserver_in_a_native_configuration
DEJAGNU=$HOME/src/runtest-gdbserver/site.exp runtest --target_board
native-gdbserver gdb.base/random-signal.exp

But that is correct, making remote.c+gdbserver correctly breakable is what the
pending patches of mine + Pedro are about.
  http://sourceware.org/ml/gdb-patches/2013-06/msg00363.html
  http://sourceware.org/ml/gdb-patches/2013-05/msg00933.html

Just so far there was no testcase affected by this remote.c+gdbserver bug.
You have implemented first testcase affected by it.

FYI I get randomly the following three cases:

-----------------------------------------------------------------
continue^M
Continuing.^M
PASS: gdb.base/random-signal.exp: continue
^C^M
Program received signal SIGINT, Interrupt.^M
main () at ./gdb.base/random-signal.c:28^M
28          ;^M
(gdb) PASS: gdb.base/random-signal.exp: stop with control-c
-----------------------------------------------------------------
continue^M
Continuing.^M
PASS: gdb.base/random-signal.exp: continue
^Cmain () at ./gdb.base/random-signal.c:28^M
28          ;^M
Quit^M
(gdb) FAIL: gdb.base/random-signal.exp: stop with control-c
-----------------------------------------------------------------
continue^M
Continuing.^M
PASS: gdb.base/random-signal.exp: continue
^CFAIL: gdb.base/random-signal.exp: stop with control-c (timeout)
-----------------------------------------------------------------

-- 
You are receiving this mail because:
You are on the CC list for the bug.