GNU bug report logs - #78381
30.1.50; Show a stack trace if an error occurs in safe hooks

Previous Next

To reply to this bug, email your comments to 78381 AT debbugs.gnu.org.

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

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

From: Daniel Mendler <mail <at> daniel-mendler.de>
To: bug-gnu-emacs <at> gnu.org
Subject: 30.1.50; Show a stack trace if an error occurs in safe hooks
Date: Sun, 11 May 2025 21:30:38 +0200

Hello!

This is a feature request to improve the situation around debugging safe
hooks. Right now if an error occurs in a safe hook occurs, only a brief
message is shown (safe_run_hooks_error in keyboard.c, "Error in %s (%S):
%S"). Would it be possible to dump a stack trace to the *Messages*
buffer? The problem is likely to avoid flooding the *Messages* buffer.
On the other hand, hooks which throw errors are disabled anyway?

Thank you!

Daniel

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Daniel Mendler <mail <at> daniel-mendler.de>
Cc: 78381 <at> debbugs.gnu.org
Subject: Re: bug#78381: 30.1.50;
 Show a stack trace if an error occurs in safe hooks
Date: Sat, 17 May 2025 12:14:07 +0300

> Date: Sun, 11 May 2025 21:30:38 +0200
> From:  Daniel Mendler via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
> 
> Hello!
> 
> This is a feature request to improve the situation around debugging safe
> hooks. Right now if an error occurs in a safe hook occurs, only a brief
> message is shown (safe_run_hooks_error in keyboard.c, "Error in %s (%S):
> %S"). Would it be possible to dump a stack trace to the *Messages*
> buffer? The problem is likely to avoid flooding the *Messages* buffer.
> On the other hand, hooks which throw errors are disabled anyway?

We have backtrace-on-redisplay-error, does that help?  If not, perhaps
a similar feature?

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

From: Daniel Mendler <mail <at> daniel-mendler.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 78381 <at> debbugs.gnu.org
Subject: Re: bug#78381: 30.1.50; Show a stack trace if an error occurs in
 safe hooks
Date: Sun, 18 May 2025 17:08:28 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

>> Date: Sun, 11 May 2025 21:30:38 +0200
>> From:  Daniel Mendler via "Bug reports for GNU Emacs,
>>  the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
>> 
>> Hello!
>> 
>> This is a feature request to improve the situation around debugging safe
>> hooks. Right now if an error occurs in a safe hook occurs, only a brief
>> message is shown (safe_run_hooks_error in keyboard.c, "Error in %s (%S):
>> %S"). Would it be possible to dump a stack trace to the *Messages*
>> buffer? The problem is likely to avoid flooding the *Messages* buffer.
>> On the other hand, hooks which throw errors are disabled anyway?
>
> We have backtrace-on-redisplay-error, does that help?  If not, perhaps
> a similar feature?

This does not help as far as I understand. But a similar variable
backtrace-on-safe-hook-error would help.

Daniel

Previous Next

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