This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 0/5][Resend] Fix multiple Ctrl-C/Quit issues


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]