From: Eli Zaretskii <eliz@gnu.org>
To: Madhu <enometh@meer.net>
Cc: emacs-devel@gnu.org
Subject: Re: Difficulty using M-x gdb
Date: Sun, 05 Feb 2023 17:33:53 +0200 [thread overview]
Message-ID: <83sffkqg7y.fsf@gnu.org> (raw)
In-Reply-To: <m3ilgggmlc.fsf@leonis4.robolove.meer.net> (message from Madhu on Sun, 05 Feb 2023 20:56:23 +0530)
> From: Madhu <enometh@meer.net>
> Date: Sun, 05 Feb 2023 20:56:23 +0530
>
>
> Wanted to mention One problem I noticed with M-x gdb is that source code
> buffers end up with permanent local binding of 'gdbmi for the variable
> gud-minor-mode, and this intercepts keys RET and tries to send them to
> the gud comint buffer even when gdb is not in action. Haven't figured
> out where this happens but I've had to overcome this by setting ``` M-:
> (setq gub-minor-mode nil) ``` in affected buffers.
On which branch? I don't see this on emacs-29, only on master (where
the changes which cause all this have not been reverted yet, in the
hope that someone will find a better way of fixing the breakage).
> [I share much the same experience with the original poster, and all my
> lost debugging skills on encountering gdb-mi like in a stroke, but I'm
> still making an effort to come to terms with gdb-mi, but its still
> uphill with 80 col screens and being limited to C-x o to switch between
> windows]
Sorry, I don't think I understand what this rant is about.
next prev parent reply other threads:[~2023-02-05 15:33 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
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 [this message]
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=83sffkqg7y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=enometh@meer.net \
/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).