GNU bug report logs - #11365
24.1.50; quitting gdb does not restore window configuration

Previous Next

Full log

Message #29 received at 11365 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: 11365 <at> debbugs.gnu.org, sds <at> gnu.org
Subject: Re: bug#11365: 24.1.50;
	quitting gdb does not restore window configuration
Date: Tue, 01 May 2012 18:54:52 +0300

> Date: Tue, 01 May 2012 10:09:01 +0200
> From: martin rudalics <rudalics <at> gmx.at>
> Cc: 11365 <at> debbugs.gnu.org
> 
>  >> Which command does "quit" run - `gdb-delete-frame-or-window'?
>  >
>  > dunno. the code indicates that, but the function seems too simple to
>  > remove all those subordinate windows and buffers.
> 
> So you have to check your key bindings ;-)

No, he doesn't.  The function to look at is gdb-reset.
(gdb-delete-frame-or-window is just what causes GDB to quit, but when
it actually does, the comint process sentinel kicks in and calls
gdb-reset.)  But for gdb-reset to do what Sam wants, gdb-setup-windows
should record the configuration of windows before it sets up the GDB
windows, otherwise we will have no information about the previous
window configuration.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.