[RFC][PATCH] GDB kills itself instead of interrupting inferior
Cyril Nikolaev
cyril@nichtverstehen.de
Fri Jul 26 23:49:00 GMT 2013
Hi Pedro,
thanks for feedback! I'm happy to see it finally fixed.
> Yep, thanks! It just needed a regression test. I went ahead and wrote
> one. I mulled over how to spawn GDB like in your reproducer (eventually
> had a wrapper shell script, and pointed the tcl GDB variable to it),
> but then realized that "set interactive-mode off" is enough to trigger
> badness
This was the thing I originally upon when I tried to write a test:
didn't find a simple way to run gdb that way from Tcl. Turning off
interactive mode with a switch is neat.
-- Cyril
On Fri, Jul 26, 2013 at 3:35 PM, Pedro Alves <palves@redhat.com> wrote:
> Hi!
> Very sorry for the slow response on this.
>
> On 02/15/2013 05:34 PM, Cyril Nikolaev wrote:
>> Hi! When GDB is run with IO redirected to a pipe, 'interrupt' command
>> causes it to kill its own process group instead of the inferior. The
>> problem manifests itself in async mode...
More information about the Gdb-patches
mailing list