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

Maciej W. Rozycki
2020-05-02T21:19:04Z

On Fri, 1 May 2020, Kevin Buettner via Gdb-patches wrote:

> I couldn't find any clue from the ChangeLog entries about why that
> break command was put into the .gdbinit file. It might be possible to
> figure out more precisely when it was introduced, but I didn't attempt
> this. I doubt that earlier imports would have any additional useful
> info not already in the ChangeLog entries that I did examine.

Hmm, I'm quite badly surprised to see this feature go, and I do hope it
has been functionally (and hopefully transparently) replaced with whatever
replaced `info_command'.

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.

So what's the current mechanism to do that? I do hope to have it the
next time I poke at GDB.

NB I fixed the mess from the `From' rewrite and cc-ed Philippe back
manually.

Maciej