GNU bug report logs - #16294
24.3.50; debugger error: "button-at: Args out of range: 0"

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 16294 in the body.
You can then email your comments to 16294 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.3.50; debugger error: "button-at: Args out of range: 0"
Date: Sun, 29 Dec 2013 14:39:33 -0800 (PST)

In the debugger (`debug', not `edebug'), I get to this:

(cond ((string-match-p "\\`[0-9a-fA-F]+\\'" input)
       (string-to-number input 16))
      ((string-match-p "^#" input)
       (read input))
      (t
       (cddr (assoc-string input mctized-cands t))))

Then, when it tried to evaluate this sexp:
(string-match-p "\\`[0-9a-fA-F]+\\'" input), which I can evaluate with
no problem using `e', the debugger is exited in error, with the
message "button-at: Args out of range: 0".

FWIW, the value of INPUT was this (a propertized string):
#("DEVICE CONTROL FOUR	^T" 0 1 (face nil) 1 21 (face nil))

(The "^T" is actually the single control character Control-T.  Changed
to the string "^T" for the bug report.)

Evaluating it using `e' returns nil, as expected.  Similarly, using `e'
I can evaluate (string-match-p "^#" input), to nil.

If I turn off debugging, the code works fine.  The debugger itself seems
to have a problem with it.

(Var `lexical-binding' is nil, here.  The code uses dynamic scoping.)


In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2013-12-27 on ODIEONE
Bzr revision: 115778 rgm <at> gnu.org-20131228000456-1797o8z6veuyozs0
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
 'CFLAGS=-O0 -g3' LDFLAGS=-Lc:/Devel/emacs/lib
 CPPFLAGS=-Ic:/Devel/emacs/include'

Message #8 received at 16294 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 16294 <at> debbugs.gnu.org
Subject: Re: bug#16294: 24.3.50;
 debugger error: "button-at: Args out of range: 0"
Date: Sat, 26 Dec 2015 02:41:40 +0100

Drew Adams <drew.adams <at> oracle.com> writes:

> In the debugger (`debug', not `edebug'), I get to this:
>
> (cond ((string-match-p "\\`[0-9a-fA-F]+\\'" input)
>        (string-to-number input 16))
>       ((string-match-p "^#" input)
>        (read input))
>       (t
>        (cddr (assoc-string input mctized-cands t))))
>
> Then, when it tried to evaluate this sexp:
> (string-match-p "\\`[0-9a-fA-F]+\\'" input), which I can evaluate with
> no problem using `e', the debugger is exited in error, with the
> message "button-at: Args out of range: 0".

Button-at?  That's weird.

Are you still seeing this problem?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #11 received at 16294 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 16294 <at> debbugs.gnu.org
Subject: RE: bug#16294: 24.3.50; debugger error: "button-at: Args out of
 range: 0"
Date: Fri, 25 Dec 2015 19:44:23 -0800 (PST)

> Button-at?  That's weird.

Yes, very.

> Are you still seeing this problem?

I have seen it recently, IIRC, but I have not seen it often.
(The context is the debugger, which I don't use all day long.)

Message #16 received at 16294 <at> debbugs.gnu.org (full text, mbox):

From: npostavs <at> users.sourceforge.net
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 16294 <at> debbugs.gnu.org
Subject: Re: bug#16294: 24.3.50;
 debugger error: "button-at: Args out of range: 0"
Date: Thu, 14 Jul 2016 19:59:11 -0400

merge 16294 23949
quit

Drew Adams <drew.adams <at> oracle.com> writes:

> In the debugger (`debug', not `edebug'), I get to this:
>
> (cond ((string-match-p "\\`[0-9a-fA-F]+\\'" input)
>        (string-to-number input 16))
>       ((string-match-p "^#" input)
>        (read input))
>       (t
>        (cddr (assoc-string input mctized-cands t))))
>
> Then, when it tried to evaluate this sexp:
> (string-match-p "\\`[0-9a-fA-F]+\\'" input), which I can evaluate with
> no problem using `e', the debugger is exited in error, with the
> message "button-at: Args out of range: 0".

This is actually the same bug as 23949, the problem is that
string-match-p let-binds inhibit-changing-match-data and causes problems
for the debugger code.
(http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23949#56)

In version 24.5, emacs -Q then evaluate (string-match-p "." nil) gives
"button-at: Args out of range: 0".  In version 25.0.95 it gives
"find-auto-coding: Wrong type argument: stringp, nil"; presumably the
specifics of the code the debugger runs changed somewhat.

Previous Next

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