From: Eli Zaretskii <eliz@gnu.org>
To: TatriX <tatrics@gmail.com>
Cc: 63084@debbugs.gnu.org
Subject: bug#63084: closed (Re: bug#64186: Patch: Suppress deprecated '-gdb-set target-async' warning message in gdb-mi.el)
Date: Thu, 13 Jul 2023 09:26:07 +0300 [thread overview]
Message-ID: <83a5w05nuo.fsf@gnu.org> (raw)
In-Reply-To: <CAG7LdX6SfYRReO9P0U64huVppV1HoWxxreQiHbY2jmZhHgxbTQ@mail.gmail.com> (message from TatriX on Tue, 11 Jul 2023 19:49:15 +0200)
> From: TatriX <tatrics@gmail.com>
> Date: Tue, 11 Jul 2023 19:49:15 +0200
> Cc: 63084@debbugs.gnu.org
>
> > So what doesn't work, and how does it not work?
> Did a few more tests to see what actually happens.
> I'm running the same code as before in "emacs -Q"
> > run &
> C-x C-a C-b ;; sets breakpoint successfully
> C-x C-a C-d ;; removes breakpoint
> > c &
> After that program continues, but 'gud-running' is now t, even if I ">
> kill" the program and "> run&" it again.
So it's a separate problem: some code sets gud-running even though
this is async mode.
Can you figure which function sets gud-running when you type "c&"? My
first suspect is gdb-starting, because it sets gud-running
unconditionally instead of doing this:
(when (not gdb-non-stop)
(setq gud-running t))
like gdb-running does. The other suspect is gdb-update-gud-running.
next prev parent reply other threads:[~2023-07-13 6:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 2:21 bug#64186: Patch: Suppress deprecated '-gdb-set target-async' warning message in gdb-mi.el Wang Diancheng
2023-06-20 7:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-20 9:25 ` Wang Diancheng
2023-06-20 9:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-20 11:55 ` Eli Zaretskii
2023-06-21 6:49 ` Wang Diancheng
2023-06-21 13:12 ` Eli Zaretskii
2023-06-28 3:51 ` Wang Diancheng
2023-06-29 6:09 ` Eli Zaretskii
2023-06-30 7:08 ` Wang Diancheng
2023-07-06 7:10 ` Eli Zaretskii
2023-04-25 19:18 ` bug#63084: 30.0.50; gud: set breakpoint while program is running tatrics
2023-04-26 6:10 ` Eli Zaretskii
2023-04-26 8:48 ` TatriX
2023-04-26 9:44 ` Eli Zaretskii
2023-04-26 11:19 ` Eli Zaretskii
2023-04-26 11:49 ` TatriX
2023-05-05 5:52 ` Eli Zaretskii
2023-05-05 5:53 ` Eli Zaretskii
2023-05-05 7:15 ` TatriX
2023-05-06 11:43 ` Eli Zaretskii
2023-05-27 21:22 ` TatriX
2023-05-28 5:28 ` Eli Zaretskii
2023-05-28 21:10 ` TatriX
2023-05-29 11:45 ` Eli Zaretskii
[not found] ` <handler.63084.D64186.168862741914107.notifdone@debbugs.gnu.org>
2023-07-11 7:31 ` bug#63084: closed (Re: bug#64186: Patch: Suppress deprecated '-gdb-set target-async' warning message in gdb-mi.el) TatriX
2023-07-11 12:24 ` Eli Zaretskii
2023-07-11 15:30 ` TatriX
2023-07-11 15:56 ` Eli Zaretskii
2023-07-11 17:49 ` TatriX
2023-07-13 6:26 ` Eli Zaretskii [this message]
2023-07-07 6:25 ` bug#64186: Patch: Suppress deprecated '-gdb-set target-async' warning message in gdb-mi.el Wang Diancheng
2023-07-07 6:42 ` Eli Zaretskii
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=83a5w05nuo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63084@debbugs.gnu.org \
--cc=tatrics@gmail.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).