From unknown Sun Jun 15 08:57:48 2025 X-Loop: help-debbugs@gnu.org Subject: bug#78381: 30.1.50; Show a stack trace if an error occurs in safe hooks Resent-From: Daniel Mendler Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 11 May 2025 19:32:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: report 78381 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: To: 78381@debbugs.gnu.org X-Debbugs-Original-To: bug-gnu-emacs@gnu.org Received: via spool by submit@debbugs.gnu.org id=B.17469918722927 (code B ref -1); Sun, 11 May 2025 19:32:02 +0000 Received: (at submit) by debbugs.gnu.org; 11 May 2025 19:31:12 +0000 Received: from localhost ([127.0.0.1]:42601 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1uECOG-0000l9-GX for submit@debbugs.gnu.org; Sun, 11 May 2025 15:31:12 -0400 Received: from lists.gnu.org ([2001:470:142::17]:46128) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1uECOA-0000jr-G4 for submit@debbugs.gnu.org; Sun, 11 May 2025 15:31:10 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1uECO4-0000Sd-AB for bug-gnu-emacs@gnu.org; Sun, 11 May 2025 15:31:00 -0400 Received: from server.qxqx.de ([2a01:4f8:c012:9177::1] helo=mail.qxqx.de) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1uECO2-0000dm-Gb for bug-gnu-emacs@gnu.org; Sun, 11 May 2025 15:31:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=daniel-mendler.de; s=key; h=Content-Type:MIME-Version:Message-ID:Date: Subject:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=tcH+a/5sK5tGf2TxKTbFdol3yMn6fk14qAEOmj6SQZo=; b=glpVQaD4zjb4bC7ZJ4eseQyIB0 sTqpgdNuy7v1ZQG9tr/2rjGhe1eMjBsb1TAawklTNvCM7Bii3MTWO1njc0eU3KAKbkedMTcAGFA5V SDUJHwbkEsW7mq23oxi62gWuL5Rb6wY6igbVVnpADDku0NHku5pPQ/es2RQdWlG11Jos=; From: Daniel Mendler Date: Sun, 11 May 2025 21:30:38 +0200 Message-ID: <874ixrt069.fsf@daniel-mendler.de> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2a01:4f8:c012:9177::1; envelope-from=mail@daniel-mendler.de; helo=mail.qxqx.de X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: 0.9 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.1 (/) 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 From unknown Sun Jun 15 08:57:48 2025 X-Loop: help-debbugs@gnu.org Subject: bug#78381: 30.1.50; Show a stack trace if an error occurs in safe hooks Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 17 May 2025 09:15:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 78381 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: To: Daniel Mendler Cc: 78381@debbugs.gnu.org Received: via spool by 78381-submit@debbugs.gnu.org id=B78381.174747325910711 (code B ref 78381); Sat, 17 May 2025 09:15:02 +0000 Received: (at 78381) by debbugs.gnu.org; 17 May 2025 09:14:19 +0000 Received: from localhost ([127.0.0.1]:45645 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1uGDcZ-0002mc-8x for submit@debbugs.gnu.org; Sat, 17 May 2025 05:14:19 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:50562) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1uGDcW-0002mK-Vu for 78381@debbugs.gnu.org; Sat, 17 May 2025 05:14:17 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1uGDcQ-0008Cv-N4; Sat, 17 May 2025 05:14:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=MYFte3AimVP7VMnF9ks/fnEgeGc/K/VadSyBw1XtJig=; b=cY+0jGSlzhsN q4+drJoV6mzlc6VXcDRNeUt5Rnv3Htg7oSQKc1ERYLEH+MPzTqkPsNDYC/+CcAcU269x7FyIm6nFt DNfK94Cnas7hQewC8ly8gM5CRLdfMlarOdt46s491Rxgn/Nw0XBD3pehj7SUXkyzS9z5uHYWMjc7M uMHRb7Awppna0KwoMwCgvPx+d+isBaYIVuHs9huWCbv3X7ZLBnsm7YYFMVU3IhR7ppumOPaDnjMEd k6MYy1254EPT/DnpaKU1BT0y+jVLtbjPGCQ0YrMYRAT5HnCCCqfK70XR5jnJFKQbo83T1NvVd1sfl tecwK9xZpLJay5A+chNuuA==; Date: Sat, 17 May 2025 12:14:07 +0300 Message-Id: <868qmvwqe8.fsf@gnu.org> From: Eli Zaretskii In-Reply-To: <874ixrt069.fsf@daniel-mendler.de> (bug-gnu-emacs@gnu.org) References: <874ixrt069.fsf@daniel-mendler.de> X-Spam-Score: -2.3 (--) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > 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" > > 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? From unknown Sun Jun 15 08:57:48 2025 X-Loop: help-debbugs@gnu.org Subject: bug#78381: 30.1.50; Show a stack trace if an error occurs in safe hooks Resent-From: Daniel Mendler Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 18 May 2025 15:09:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 78381 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: To: Eli Zaretskii Cc: 78381@debbugs.gnu.org Received: via spool by 78381-submit@debbugs.gnu.org id=B78381.174758093030647 (code B ref 78381); Sun, 18 May 2025 15:09:02 +0000 Received: (at 78381) by debbugs.gnu.org; 18 May 2025 15:08:50 +0000 Received: from localhost ([127.0.0.1]:59104 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1uGfdC-0007yE-3A for submit@debbugs.gnu.org; Sun, 18 May 2025 11:08:50 -0400 Received: from server.qxqx.de ([2a01:4f8:c012:9177::1]:55419 helo=mail.qxqx.de) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1uGfd8-0007xe-Jh for 78381@debbugs.gnu.org; Sun, 18 May 2025 11:08:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=daniel-mendler.de; s=key; h=Content-Type:MIME-Version:Message-ID:Date: References:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=4uzH/WvJXiHS+xXRskKrry+ZNwa/NQAuCfc7dontrlQ=; b=BtrJHGPZkQWttKJn/1HQ6wG+lp BxsVeteypeS4Ma8R1vKkwtyofT69bEZnOHZdGVe7nDHPeBpPTvcgnoIEflmP/SFxERuVktDwkWlyE uGqZ/yi/TVXUqHKSEyl5tju7np49ucSJ15oOsMrAulsJA2BdaJg+0pCQhHJv12+8/r+o=; From: Daniel Mendler In-Reply-To: <868qmvwqe8.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 17 May 2025 12:14:07 +0300") References: <874ixrt069.fsf@daniel-mendler.de> <868qmvwqe8.fsf@gnu.org> Date: Sun, 18 May 2025 17:08:28 +0200 Message-ID: <87iklyardf.fsf@daniel-mendler.de> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) Eli Zaretskii 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" >> >> 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