From: Eli Zaretskii <eliz@gnu.org>
To: Michael Welsh Duggan <mwd@md5i.com>
Cc: emacs-devel@gnu.org
Subject: Re: Difficulty using M-x gdb
Date: Wed, 01 Feb 2023 19:07:18 +0200 [thread overview]
Message-ID: <83pmatz54p.fsf@gnu.org> (raw)
In-Reply-To: <87357pqvxq.fsf@md5i.com> (message from Michael Welsh Duggan on Wed, 01 Feb 2023 09:53:05 -0500)
> From: Michael Welsh Duggan <mwd@md5i.com>
> Date: Wed, 01 Feb 2023 09:53:05 -0500
>
> When I step through a program, the interface keeps track of where I am
> in the source buffer. But, when the program produces output, it
> replaces the source buffer window with an input/output buffer window
> which is dedicated. The only way I have found out to display the source
> buffer again is to use "M-x gdb-restore-windows". In code that is doing
> a fair amount of output, this is very tedious.
>
> What is right way to handle this?
Try "M-x gdb-display-io-buffer RET". (You can also activate that
window (or any other gdb-mi window) via the menu bar's
Gud->GDB-Windows menu.)
> If it requires customization, why is
> customization needed to make this fairly common case work well?
Not every program communicates via stdin/stdout, and when a program
doesn't, popping up another window would be a nuisance, I think.
> Maybe most importantly, this input/output buffer/window doesn't seem
> to be mentioned in the Emacs documentation at all.
It is mentioned, but maybe not prominently enough. Patches welcome,
or I will get to adding that soon.
> I have my suspicions that, once I get used to the new interface, I might
> like using it, but right now I'm having difficulty figuring out what
> habits I need to relearn.
My suggestion is to start with gdb-many-windows, and then close those
windows you don't need.
next prev parent reply other threads:[~2023-02-01 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 14:53 Difficulty using M-x gdb Michael Welsh Duggan
2023-02-01 17:07 ` Eli Zaretskii [this message]
2023-02-01 23:18 ` Yuan Fu
2023-02-01 23:53 ` Dmitry Gutov
2023-02-02 0:18 ` Dmitry Gutov
2023-02-02 18:50 ` Eli Zaretskii
2023-02-05 15:26 ` Madhu
2023-02-05 15:33 ` Eli Zaretskii
2023-02-06 23:23 ` Madhu
2023-02-03 21:35 ` Konstantin Kharlamov
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=83pmatz54p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mwd@md5i.com \
/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.