GNU bug report logs - #40250
26.3; gdb-mode incorrectly handles gdb's `explore' command

Previous Next

Full log

View this message in rfc822 format

From: Vladimir Nikishkin <lockywolf <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 40250 <at> debbugs.gnu.org
Subject: bug#40250: 26.3; gdb-mode incorrectly handles gdb's `explore' command
Date: Sat, 28 Mar 2020 21:34:54 +0800

I didn't test it extensively, but seems be to working.

сб, 28 мар. 2020 г. в 21:05, Eli Zaretskii <eliz <at> gnu.org>:
>
> > From: Vladimir Nikishkin <lockywolf <at> gmail.com>
> > Date: Fri, 27 Mar 2020 15:25:05 +0800
> >
> > 2) run M-x gdb RET RET
> > 3)break 14
> > (should put a breakpoint at the print statement)
> > 4)run RET
> > 5)explore a
> > (a is the specially prepared data object)
> > gdb should ask you for a choice
> > 6)0
> > (the only choice)
> >
> > Expected result: display of the contents of a
> > Obtained result: silent return to the (gdb) prompt
>
> Thanks.  Does the change below fix this?
>
> diff --git a/lisp/progmodes/gdb-mi.el b/lisp/progmodes/gdb-mi.el
> index 7fb3687..e046264 100644
> --- a/lisp/progmodes/gdb-mi.el
> +++ b/lisp/progmodes/gdb-mi.el
> @@ -1849,7 +1849,7 @@ gdb-control-commands-regexp
>     "comm\\(a\\(n\\(ds?\\)?\\)?\\)?\\|if\\|while"
>     "\\|def\\(i\\(ne?\\)?\\)?\\|doc\\(u\\(m\\(e\\(nt?\\)?\\)?\\)?\\)?\\|"
>     gdb-python-guile-commands-regexp
> -   "\\|while-stepping\\|stepp\\(i\\(ng?\\)?\\)?\\|ws\\|actions"
> +   "\\|while-stepping\\|stepp\\(i\\(ng?\\)?\\)?\\|ws\\|actions\\|explore"
>     "\\)\\([[:blank:]]+\\([^[:blank:]]*\\)\\)?$")
>    "Regexp matching GDB commands that enter a recursive reading loop.
>  As long as GDB is in the recursive reading loop, it does not expect



-- 
Yours sincerely, Vladimir Nikishkin

Previous Next

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