From: Eli Zaretskii <eliz@gnu.org>
To: diancheng_wang@163.com
Cc: 74642@debbugs.gnu.org
Subject: bug#74642: 31.0.50; [Patch] Turn off current source line indicator when gdb buffer is killed
Date: Wed, 04 Dec 2024 21:11:35 +0200 [thread overview]
Message-ID: <86ed2nz2jc.fsf@gnu.org> (raw)
In-Reply-To: <8634j31s75.fsf@gnu.org> (message from Eli Zaretskii on Wed, 04 Dec 2024 15:41:18 +0200)
> Cc: 74642@debbugs.gnu.org
> Date: Wed, 04 Dec 2024 15:41:18 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> > From: Diancheng Wang <diancheng_wang@163.com>
> > Cc: 74642@debbugs.gnu.org
> > Date: Wed, 04 Dec 2024 16:22:51 +0800
> >
> > > I guess you mean "C-x k RET"?
> >
> > Yes, I mean "C-x k RET"
> >
> > >
> > > When I do that, Emacs asks me whether to kill the process associated
> > > with the buffer, and if I say YES, the indicator does disappear
> >
> > Yes, the steps are same with me.
> >
> > > (sometimes after a second, which I guess is needed for Emacs to kill
> > > the process). Isn't that what you see?
> >
> > No, the indicator does not disappear after I killed "*gud-myprogram*" buffer.
> > By the way I started emacs using "emacs -Q".
>
> So did I.
>
> > The attachment is my running emacs information (the buffer content
> > created by report-emacs-bug)
>
> Looks like some kind of regression in Emacs 31. It works in Emacs 30.
> If you could bisect to find the offending commit, it will be
> appreciated.
Crystal ball says that the regression was caused by the change you
submitted (and I installed) in bug#73687. It added a call to
gud-hide-current-line-indicator to gdb-starting and to gud-sentinel.
Could you try reverting those changes and see if that solves the
problem in Emacs 31?
next prev parent reply other threads:[~2024-12-04 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 7:04 bug#74642: 31.0.50; [Patch] Turn off current source line indicator when gdb buffer is killed Diancheng Wang
2024-12-02 13:17 ` Eli Zaretskii
2024-12-03 2:04 ` Diancheng Wang
2024-12-03 12:32 ` Eli Zaretskii
2024-12-04 8:22 ` Diancheng Wang
2024-12-04 13:41 ` Eli Zaretskii
2024-12-04 19:11 ` Eli Zaretskii [this message]
2024-12-05 7:34 ` Diancheng Wang
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=86ed2nz2jc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74642@debbugs.gnu.org \
--cc=diancheng_wang@163.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 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).