Re: [PATCH 3/3] Fix control-c handling on Windows

[Tom Tromey <tromey@adacore.com>]

Hannes> Again, I wasn't clear enough here.
Hannes> The difference is not because of i686 and x86_64, but that the x86_64 build
Hannes> has TUI+python enabled, but my i686 build has not.

>> Aha, I see, thanks.

Today I built an x86-64 Windows gdb, but I disabled Python.  I already
had the TUI disabled for Windows.

I used RDP and started powershell, then ran gdb there.  I did 6 tests: a
C-c and a C-break test of "run", "run" with "set new-console 1", and
"attach" -- and in all these cases, it worked.

So now I'm wondering again what the difference could be between our
situations.

>> Anyway I am wondering if we can have gdb_rl_deprep_term_function call
>> rl_clear_signals and then reinstall the gdb signal handlers.  This idea
>> makes me wonder if we even need SetConsoleCtrlHandler at all -- maybe gdb
>> could just use signal after all.

Hannes> Good question, maybe it doesn't handle C-break as well?

C-break can work with signal by installing a handler for SIGBREAK.  This
worked fine when I tried it, but the issue was still that the SIGINT
handler somehow stopped working.

Tom