From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Insight into the mystery hangs Date: Mon, 12 Feb 2024 14:52:59 +0200 Message-ID: <868r3psv2s.fsf@gnu.org> References: <20240211213737.3A38C18A1647@snark.thyrsus.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1605"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: "Eric S. Raymond" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Feb 12 13:53:48 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rZVoi-0000DD-Me for ged-emacs-devel@m.gmane-mx.org; Mon, 12 Feb 2024 13:53:48 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rZVo0-0005HT-DP; Mon, 12 Feb 2024 07:53:04 -0500 Original-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 1rZVnx-0005GN-Uw for emacs-devel@gnu.org; Mon, 12 Feb 2024 07:53:01 -0500 Original-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 1rZVnx-00016H-F1; Mon, 12 Feb 2024 07:53:01 -0500 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=nX3hKLKni+Ez66leiLqdYfZ9AVGLmJTv2cL+UdFxGKo=; b=UF4bfHHON2bF gJRVi9dGGXIzkHxq6vIMtmtxvi76+e6tjwU9y9IVJ7VD7UsIxxT4K2xXXgTX34auxRRpQewlOfV4L ScHryhYZ0GHwnnLvKnsfK8kOVl4rcZ+G9zc8GeUfEglWrl5TnzhITMzftWbY8Nr4FQiMJAMyEqy8V fMIGpDEIyNNYPrNva2QAIHSe4Iy7Jii4m9OmRpVlScOVRUVPoEf4FIA3ZeslIeXtyZy/PkgGOewoD BWMAXHOy3VMjCP0hjEh/GcCQ1OuQBopWFJvibKV3Z6lVvDYs5Xseq8KYjWqPccfvR69uj4jjvY8VJ HwXXKJTiOgVGLq+lrtuR4Q==; In-Reply-To: <20240211213737.3A38C18A1647@snark.thyrsus.com> (esr@thyrsus.com) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:316130 Archived-At: > From: "Eric S. Raymond" > Date: Sun, 11 Feb 2024 16:37:37 -0500 (EST) > > However. Emacs is not entirely off the hook here. When I'm not under > deadline pressure I will file a bug with a title something like > "With debug-on-quit enabled, Emacs does not reliably raise a debug > trace on interrupt of call-process" Isn't that call issued from the mode-line display? If so, that is done from redisplay, and redisplay cannot enter debugger, so it catches all errors. If you want to produce Lisp backtraces from Lisp code called by redisplay, you need to use the facilities documented in the node "Debugging Redisplay" in the ELisp Reference manual.