This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 0/5][Resend] Fix multiple Ctrl-C/Quit issues
- From: Pedro Alves <palves at redhat dot com>
- To: GDB Patches <gdb-patches at sourceware dot org>
- Date: Thu, 16 Nov 2017 18:47:19 +0000
- Subject: Re: [PATCH 0/5][Resend] Fix multiple Ctrl-C/Quit issues
- Authentication-results: sourceware.org; auth=none
- References: <1510010836-15287-1-git-send-email-palves@redhat.com>
On 11/06/2017 11:27 PM, Pedro Alves wrote:
> As I mentioned before, I've been messing with GDB's terminal handling
> in context of multi-target. While doing some inflow.c surgery, I had
> the bright idea of writing a test that did:
>
> break foo
> commands
> printf "hello\n"
> continue
>
> and run that against a program that does basically:
>
> while (1)
> foo ();
>
> and then while the inferior is running and hitting that breakpoint,
> hit Ctrl-C, to make sure target_terminal::inferior/ours handling was
> correct and that the user always re-gained control.
>
> Unfortunately, that test hit a number of other, preexisting
> problems... (I never learn... :-P) This series fixes them, and then
> adds a testcase similar to the above. The test passes cleanly with
> the fixes in place, but fails otherwise.
>
> Pedro Alves (5):
> Fix swallowed "Quit" when inserting breakpoints
> Fix stdin ending up not registered after a Quit
> Don't ever Quit out of resume
> Python unwinder sniffer: PyExc_KeyboardInterrupt -> Quit
> Test breakpoint commands w/ "continue" + Ctrl-C
I've pushed these in as well.
Thanks,
Pedro Alves