GNU bug report logs -
#63084
30.0.50; gud: set breakpoint while program is running
Previous Next
Reported by: tatrics <at> gmail.com
Date: Wed, 26 Apr 2023 03:56:03 UTC
Severity: normal
Merged with 64186
Found in version 30.0.50
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #46 received at control <at> debbugs.gnu.org (full text, mbox):
merge 64186 63084
thanks
> From: Wang Diancheng <dianchengwang <at> gmail.com>
> Date: Wed, 21 Jun 2023 14:49:01 +0800
> Cc: luangruo <at> yahoo.com, 64186 <at> debbugs.gnu.org
>
> Eli Zaretskii <eliz <at> 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.
This bug report was last modified 1 year and 316 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.