GNU bug report logs - #32576
24.5; cannot end gdb breakpoint command list

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#13569: closed (24.3.50; gdb-control-commands-regexp has a typo)
Date: Mon, 10 Sep 2018 13:13:03 +0000

[Message part 1 (text/plain, inline)]

Your message dated Mon, 10 Sep 2018 16:12:36 +0300
with message-id <83zhwpo5rv.fsf <at> gnu.org>
and subject line Re: bug#32576: 24.5; cannot end gdb breakpoint command list
has caused the debbugs.gnu.org bug report #32576,
regarding 24.3.50; gdb-control-commands-regexp has a typo
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
32576: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=32576
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: emacs18 <at> gmail.com
To: bug-gnu-emacs <at> gnu.org
Subject: 24.3.50; gdb-control-commands-regexp has a typo
Date: Sun, 27 Jan 2013 13:21:00 -0800

I use latest bzr trunk and emacs-24 branches on linux.

I believe the following patch should be applied to remove "s" from
"commands" portion of a regexp:

	=== modified file 'lisp/progmodes/gdb-mi.el'
	--- lisp/progmodes/gdb-mi.el	2013-01-11 23:08:55 +0000
	+++ lisp/progmodes/gdb-mi.el	2013-01-27 21:16:01 +0000
	@@ -1680,7 +1680,7 @@
	 (defvar gdb-control-commands-regexp
	   (concat
	    "^\\("
	-   "commands\\|if\\|while\\|define\\|document\\|python\\|"
	+   "command\\|if\\|while\\|define\\|document\\|python\\|"
	    "while-stepping\\|stepping\\|ws\\|actions"
	    "\\)\\([[:blank:]]+.*\\)?$")
	   "Regexp matching GDB commands that enter a recursive reading loop.

Why?  Because without this change, gdb fails to handle the command
"command" incorrectly.  gdb's "command" allows one to associate a gdb
command sequence with a breakpoint.  Following is how it should work
to add "print foo" command for breakpoint number 2 while debugging a C
program:

    (gdb) command 2
    print foo
    end
    (gdb)

where as soon as "end" is typed, "command" should be terminated and
"(gdb) " prompt printed.  Instead of this what happens is that "(gdb)
" prompt is never printed and it acts as if "end" is not treated as
the terminating special command, i.e., this is what I see:

    (gdb) command 2
    print foo
    end

At this point gdb seems hung.  The only way to get back the gdb prompt
is to hit Control-C twice.

This bug has been around for several weeks at least on both emacs-24
and trunk bzr branchs of emacs.

[Message part 3 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: rgm <at> gnu.org
Cc: 32576-done <at> debbugs.gnu.org, legowik <at> roboticresearch.com
Subject: Re: bug#32576: 24.5; cannot end gdb breakpoint command list
Date: Mon, 10 Sep 2018 16:12:36 +0300

> Date: Wed, 29 Aug 2018 21:45:01 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: 32576 <at> debbugs.gnu.org, legowik <at> roboticresearch.com
> 
> > From: Glenn Morris <rgm <at> gnu.org>
> > Cc: Steven Legowik <legowik <at> roboticresearch.com>,  32576 <at> debbugs.gnu.org
> > Date: Wed, 29 Aug 2018 14:11:13 -0400
> > 
> > 
> > AFAICS it remains broken in master.
> > You have to type "commands" not "command" to get it to work.
> > gdb-control-commands-regexp doesn't handle abbreviations.
> > 
> > This is a duplicate of bug#20807.
> 
> If that's the problem, I wonder why no one fixed it until now.

Fixed on the emacs-26 branch.

Previous Next

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