GNU bug report logs - #40088
27.0.90; Symbol’s value as variable is void: debugger-outer-match-data

Previous Next

Full log

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

From: Noam Postavsky <npostavs <at> gmail.com>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: Joost Kremers <joostkremers <at> fastmail.fm>, 40088 <at> debbugs.gnu.org
Subject: Re: bug#40088: 27.0.90; Symbol’s value as
 variable is void: debugger-outer-match-data
Date: Tue, 17 Mar 2020 07:44:01 -0400

Michael Heerdegen <michael_heerdegen <at> web.de> writes:

> Joost Kremers <joostkremers <at> fastmail.fm> writes:
>
>> *** Eval error ***  Symbol’s value as variable is void:
>> debugger-outer-match-data
>
> Another defvar with a missing init value so the variable is not globally
> special?  Or is this case intentional for some reason?

It's something more complicated than that I think.  There are some extra
errors that get raised during the handling of the initial inciting
error, that somehow ends in inhibit-debugger being left set to t.  So
some spec/let-binding is getting snuck out of incorrectly perhaps?

It seems to be ielm specific, but I guess ielm just happens to be doing
something tricky enough to trigger the real bug which lies elsewhere.
As a workaround, you can (setq inhibit-debugger nil) after the first
failure happens.

I can't trigger the debugger-outer-match-data error in Emacs 26, but the
debugger doesn't seem to trigger from ielm at all in that version.

Previous Next

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