GNU bug report logs - #65612
gdb-mi non-stop mode can not set breakpoints when `gud-running' is t

Previous Next

Full log

Message #10 received at 65612-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Diancheng Wang <diancheng_wang <at> 163.com>
Cc: 65612-done <at> debbugs.gnu.org
Subject: Re: bug#65612: gdb-mi non-stop mode can not set breakpoints when
 `gud-running' is t
Date: Thu, 31 Aug 2023 13:13:11 +0300

> From: Diancheng Wang <diancheng_wang <at> 163.com>
> Date: Wed, 30 Aug 2023 10:15:01 +0800
> 
> When gdb-mi is running in non-stop mode (both `gud-running' and
> `gdb-non-stop' are t), it can not set breakpoints using `gud-break'
> function. But at the same situation, we can set breakpoints using gdb
> CLI commands in gdb interactive buffer.
> 
> Attached patch fixed this bug. The patch introduces a gud new variable:
> `gud-async-running'.  The marco `gud-def' still sends command to gdb if
> `gud-async-running' is t even `gud-running' is t.

Thanks, installed on the master branch and closing the bug.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.