[PATCH 0/2] Debuggers and ctrl-C

[Eric Pouech]

WineDbg both in regular mode and in gdb proxy mode, no longer
properly reacts to ctrl-c (which is supposed when debuggee is running,
to stop the debuggee execution and reenter debugger where the debuggee
has stopped).
Currently, it just terminates WineDbg (and gdb in proxy mode).

First, start.exe, for any child process shouldn't handle the ctrl-c event.
It's up to child to decide what to do with it. Quitting start.exe too early
detaches all start.exe's children and grand* children from the Unix
console, which prevents any user input.

Then in proxy mode, only gdb should handle ctrl-c (winedbg must be
transparent).

With those two patches applied, both situations are now properly handled.

A+
---

Eric Pouech (2):
      programs/start: ignore Ctrl-C and let the child decides what to do with it.
      programs/winedbg: in gdb proxy mode, ignore ctrl-c


 programs/start/start.c      | 1 +
 programs/winedbg/gdbproxy.c | 2 ++
 2 files changed, 3 insertions(+)