From: Noam Postavsky <npostavs@gmail.com>
To: Miles Bader <miles.bader@necel.com>
Cc: 2556@debbugs.gnu.org, Miles Bader <miles@gnu.org>
Subject: bug#2556: 23.0.91; gdb-ui sometimes messes up window handling
Date: Sun, 20 May 2018 20:18:49 -0400 [thread overview]
Message-ID: <878t8dj1xy.fsf@gmail.com> (raw)
In-Reply-To: <buoocwiri8a.fsf@dhlpc061.dev.necel.com> (Miles Bader's message of "Tue, 03 Mar 2009 19:52:37 +0900")
tags 2556 + unreproducible
quit
Miles Bader <miles.bader@necel.com> writes:
> This is an old bug with gdb-ui that seems to have been forgotten (but is
> still present though; it bites me regularly); the basic symptom is that
> sometimes when you type a command to a gud debugger prompt, and gud pops
> up an associated source code buffer, the source code buffer will be
> displayed in the same window where your gud session buffer was displayed,
> resulting in the gud buffer being hidden!
>
>
> Here's the test case I gave (starting with emacs -Q):
>
> (1) start a gdb session in emacs, and hit a breakpoint or something so
> that gdb pops up the source in another window (splitting the frame)
>
> (2) Switch to the source window with "C-x o"
>
> (3) Delete the other [*gud...*] window with "C-x 1"
>
> (4) Switch back to the *gud...* buffer using "C-x b *gud...* RET"
>
> (5) Try to pop up the source buffer again using a gdb command, e.g.,
> just "frame RET".
>
> *bang*, *gdb...* buffer disappears, source buffer is only ting
> displayed... :-(
I'm not able to reproduce this in more recent Emacs versions (I've
tested back to 24.3).
next prev parent reply other threads:[~2018-05-21 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 10:52 bug#2556: 23.0.91; gdb-ui sometimes messes up window handling Miles Bader
2009-03-08 2:06 ` Nick Roberts
2009-03-08 7:20 ` Miles Bader
2014-11-09 6:20 ` Alexandre BACQUART
2018-05-21 0:20 ` Noam Postavsky
2018-05-21 0:18 ` Noam Postavsky [this message]
2022-01-27 19:17 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878t8dj1xy.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=2556@debbugs.gnu.org \
--cc=miles.bader@necel.com \
--cc=miles@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.