Re: Extend gdb to filter registers

[Yuan Fu]

> On Jan 31, 2020, at 8:58 AM, Eli Zaretskii <address@hidden> wrote:
> 
>> From: Yuan Fu <address@hidden>
>> Date: Sat, 25 Jan 2020 17:34:13 -0500
>> Cc: address@hidden,
>> address@hidden,
>> address@hidden,
>> address@hidden,
>> address@hidden
>> 
>>> No, the usual complaint is that gdb-mi messes up windows during the
>>> debugging session itself.  E.g., if you had several source files
>>> displayed in carefully configured windows on a frame, starting
>>> "M-x gdb" will typically mess up your window configuration on that
>>> frame.  Using a separate frame works around that.
>> 
>>>> That’s not hard to fix since we
>>>> have window-configurations now. I have a patch that makes gdb preserves 
>>>> window configuration that the user
>>>> had prior to starting gdb.
>>> 
>>> That could be another way, but running a debugging session usually
>>> benefits from maximizing the frame.  Will your patch undo that as well?
>> 
>> No, I simply save the window configuration at gdb start up by 
>> `window-state-get` and restores it when gdb quits. If gdb doesn’t maximize 
>> the frame, it shouldn’t un-maximize the frame after it quits either. If you 
>> want to make gdb maximize the frame by default, then gdb should un-maximize 
>> the frame after it quits. What I want to say is, who makes the change, who 
>> is responsible for it.
> 
> But we already have gdb-restore-windows, so it sounds like users
> already can restore their window configuration.  Why do we need
> anything else?

Hmmm, which window configuration are you referring to? gdb-restore-windows 
restores the window configuration you have after M-x gdb, not the one before 
M-x gdb. I want gdb to restore the latter after it quits.

Yuan