unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Welsh Duggan <mwd@md5i.com>
To: emacs-devel@gnu.org
Subject: Difficulty using M-x gdb
Date: Wed, 01 Feb 2023 09:53:05 -0500	[thread overview]
Message-ID: <87357pqvxq.fsf@md5i.com> (raw)

I have used "M-x gud-gdb" to run gdb for many years.  I used it for
quite a while after the gdb-mi interface was added due to its ability to
debug the same program multiple times at the same time in the same
Emacs.  I don't need that capability right now. 

Due to a bug in `gud-gdb` (#61162) I am trying to switch to "M-x gdb"
instead.  Unfortunately, I can't really figure out how to make this work
in a way that makes sense to me.  `gdb-many-windows` being nil is the
default, and the default should be reasonably easy to use (one would
hope), but I am having the following problem:

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?  If it requires customization, why is
customization needed to make this fairly common case work well?  Is
there a way to make output go the interaction buffer?  Maybe most
importantly, this input/output buffer/window doesn't seem to be
mentioned in the Emacs documentation at all.

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.

-- 
Michael Welsh Duggan
(md5i@md5i.com)



             reply	other threads:[~2023-02-01 14:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01 14:53 Michael Welsh Duggan [this message]
2023-02-01 17:07 ` Difficulty using M-x gdb Eli Zaretskii
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87357pqvxq.fsf@md5i.com \
    --to=mwd@md5i.com \
    --cc=emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).