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

Previous Next

Full log

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

From: Stefan Kangas <stefan <at> marxist.se>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: Brady Trainor <mail <at> bradyt.com>, 32030-done <at> debbugs.gnu.org
Subject: Re: bug#32030: 27.0.50; debug-on-signal, void-variable
Date: Wed, 21 Aug 2019 04:22:19 +0200

Noam Postavsky <npostavs <at> gmail.com> writes:

> forwarded 32030 https://github.com/nex3/dart-mode/issues/30
> quit
>
> On 2 July 2018 at 01:38, Noam Postavsky <npostavs <at> gmail.com> wrote:
>
>> If this is getting called from redisplay, I think the debugger might be
>> suppressed from that context, even if you set debug-on-signal.  I seem
>> to recall triggerring refontification synchronously with M-o M-o
>> (font-lock-fontify-block) worked for me in a similar situation (although
>> it's possible you won't hit the error this way).
>
> I can get a backtrace this way, I posted to the dart-mode issue:
>
> https://github.com/nex3/dart-mode/issues/30#issuecomment-403521238

This issue seems to not be related to a third party package (and the
link to the issue in the dart-mode issue tracker has additionally now
been fixed).  I'm therefore closing this bug report.

Thanks,
Stefan Kangas

Previous Next

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