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

[Pedro Alves <palves@redhat.com>]

On 5/3/20 1:13 AM, Maciej W. Rozycki wrote:

>  I don't remember offhand; I do remember there were issues in some debug 
> scenarios with using signals, perhaps unintended delivery to the debuggee 
> GDB (or its debuggee), or some problems with trapping the signal in the 
> first place (perhaps on MinGW, where obviously we don't have a typical 
> *nix environment and ^C may have simply killed the outer GDB and other 
> signals such as SIGQUIT may not have had a way to be produced at all).  
> Especially as when debugging broken GDB (which is why you debug it in the 
> first place) you often find it in an odd state.

Exactly.  I've used this feature in scenarios like you describe.  I'm
also surprised people weren't aware of the feature, and would like it
restored somehow.

> commit 0a7cfe2cf50b450d0cf9db16ee4bd027e08763e8
> Author: Stan Shebs <shebs@codesourcery.com>
> Date:   Mon Sep 16 18:00:34 2013 +0000
> 
> so we have removed that piece of documentation from our repo, however as 
> per: <https://sourceware.org/ml/gdb-patches/2013-08/msg00855.html> it has 
> been moved to our wiki and the feature of `info' is still mentioned here: 
> <https://sourceware.org/gdb/wiki/Internals%20Debugging-GDB-with-itself>.
> 
>  So it looks like we've actually removed a documented feature.

Thanks for finding it.

Pedro Alves