From: Eli Zaretskii <eliz@gnu.org>
To: Wang Diancheng <dianchengwang@gmail.com>
Cc: luangruo@yahoo.com, 64186@debbugs.gnu.org
Subject: bug#64186: Patch: Suppress deprecated '-gdb-set target-async' warning message in gdb-mi.el
Date: Wed, 21 Jun 2023 16:12:12 +0300 [thread overview]
Message-ID: <83wmzx3qoj.fsf@gnu.org> (raw)
In-Reply-To: <CADmgXh4T0s5_y__TCf1+iMHi9YVwTAirGRrYiykGCYw6dQ2aHg@mail.gmail.com> (message from Wang Diancheng on Wed, 21 Jun 2023 14:49:01 +0800)
merge 64186 63084
thanks
> From: Wang Diancheng <dianchengwang@gmail.com>
> Date: Wed, 21 Jun 2023 14:49:01 +0800
> Cc: luangruo@yahoo.com, 64186@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> 于2023年6月20日周二 19:55写道：
> >
> > Given all that mess, I wonder if "M-x gdb" in its current shape indeed
> > supports the asynchronous execution. If it doesn't, we may be better
> > off not sending that command at all for now, until bug#63084 is fixed.
>
> Yes, I agree. Currently gdb-mi doesn't actually support asynchronous
> execution because of bug#63084. Before it is fixed, to suppress the
> annoying warning, we can set gdb-non-stop-setting to nil as a
> workaround.
Thanks, I've now done so on the emacs-29 branch. I will leave this
bug open (and merge it to bug#63084), so that they could be fixed in
the future, hopefully not too distant future.
next prev parent reply other threads:[~2023-06-21 13:12 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 [this message]
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
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=83wmzx3qoj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64186@debbugs.gnu.org \
--cc=dianchengwang@gmail.com \
--cc=luangruo@yahoo.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).