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: Why is it so difficult to get a Lisp backtrace? Date: Sun, 26 Jun 2022 08:20:47 +0300 Message-ID: <83o7yg9f0w.fsf@gnu.org> References: <87edzchi3d.fsf@gnus.org> <83sfnsadow.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1269"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 26 07:22:06 2022 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 1o5Kij-000Ad5-VJ for ged-emacs-devel@m.gmane-mx.org; Sun, 26 Jun 2022 07:22:06 +0200 Original-Received: from localhost ([::1]:56086 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o5Kih-0002l9-Ne for ged-emacs-devel@m.gmane-mx.org; Sun, 26 Jun 2022 01:22:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48338) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o5KhZ-00020C-SV for emacs-devel@gnu.org; Sun, 26 Jun 2022 01:20:53 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:44148) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o5KhV-0001U8-Kc; Sun, 26 Jun 2022 01:20:52 -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=UZLBQkE8RCQnkIyvItFrpUIfbwiY8OAiXWTizHKrCIg=; b=gL1BVEwJcezI JB9DKRuUcApaadBvMyrZfhIe4yJizouvNF0g2RixoFujrz36R8gJH97gGsYhTQqd4rilpQmfiwNNj rtiHFSdPPmVrwpxMkrqxDpBSjZWTeVu0AYcsDNZ7gEXKeyrVuKWgbLZPBoGQGew9Na5ySP/+FYHPZ X2x62QPHbbDiNtYiNS9l690NTJEWxfsTdZaMqthA7S9NWx4P0ZLc/s9uBiFxzWIGgvyHW1RKiep+b yi6jVnjEUN8J4wBZtB91AE/QFlt2oCXXpTYOeDSyvHwwP2nSOVcZd0hnux0ZmwHqJerbT/RArTyWH OUtdmySraV98m1pqb4Io0g==; Original-Received: from [87.69.77.57] (port=3706 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o5KhT-00045q-NK; Sun, 26 Jun 2022 01:20:48 -0400 In-Reply-To: (message from Alan Mackenzie on Sat, 25 Jun 2022 19:45:49 +0000) 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" Xref: news.gmane.io gmane.emacs.devel:291625 Archived-At: > Date: Sat, 25 Jun 2022 19:45:49 +0000 > Cc: larsi@gnus.org, emacs-devel@gnu.org > From: Alan Mackenzie > > > The only two ways of having that, AFAIK, are: > > > . emit the backtrace int *Messages* > > . add the backtrace to delayed-warnings-list > > Why can't the backtrace be generated and stored, and only displayed at a > subsequent redisplay (probably the next one)? That's what the second alternative above already does.