GNU bug report logs - #32030
27.0.50; debug-on-signal, void-variable

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: mail <at> bradyt.com, 32030 <at> debbugs.gnu.org
Subject: Re: bug#32030: 27.0.50; debug-on-signal, void-variable
Date: Mon, 02 Jul 2018 17:37:44 +0300

> From: Noam Postavsky <npostavs <at> gmail.com>
> Date: Mon, 02 Jul 2018 01:38:51 -0400
> Cc: 32030 <at> debbugs.gnu.org
> 
> Brady Trainor <mail <at> bradyt.com> writes:
> 
> > Reduction? Hmm. Dart-mode is provoking error messages related to
> > jit-lock, and sending them to Messages buffer (the issue from tracker
> > I'm currently reproducing is when dart-mode is applied to a buffer with
> > string interpolation). I was trying to make a minimal broken example
> > more obvious with debugger opening on startup. Maybe we can set that
> > variable closer the moment dart-mode is called, when the trace is
> > preferred.
> 
> If this is getting called from redisplay, I think the debugger might be
> suppressed from that context, even if you set debug-on-signal.

Indeed, because starting a debugger requires redisplay, which will
again signal an error, which will again attempt to enter the debugger,
...

Previous Next

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