Re: [PUSHED/OBVIOUS] Remove gdb-gdb.gdb breakpoint on disappeared function info_command.

Kevin Buettner
2020-05-02T23:57:20Z

On Sun, 03 May 2020 01:01:26 +0200
Philippe Waroquiers <philippe.waroquiers@skynet.be> wrote:

> On Sat, 2020-05-02 at 22:19 +0100, Maciej W. Rozycki wrote:
>
> > Its use was quite obvious to anyone who actually debugged GDB from time
> > to time: it was there so that you could break from the debuggee GDB into
> > the debugger GDB with the use of the `info' command (with no arguments),
> > as obviously using signals like SIGINT for that was quite problematic. I
> > used to use this feature regularly, up until the last time a couple months
> > back when I switched to non-GDB work.
> I do limited GDB debugging, but was not aware of this feature.
> I am not sure to understand the problem:
> C-c works for me to interrupt GDB, and the top GDB gets
> back the control (I typically launch top-gdb separately
> and attach to the inferior GDB).

FWIW, I also use Ctrl-C do get back to the top GDB.

I'd also like to understand the use case when this is problematic.

Kevin