From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#61847: debug-early-backtrace only works some of the time. Date: Tue, 28 Feb 2023 14:58:31 -0500 Message-ID: References: Reply-To: Stefan Monnier Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="354"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 61847@debbugs.gnu.org To: Alan Mackenzie Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Feb 28 20:59:22 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1pX689-000AXE-Vx for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 28 Feb 2023 20:59:22 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pX67r-0003bn-Ft; Tue, 28 Feb 2023 14:59:03 -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 1pX67q-0003be-GH for bug-gnu-emacs@gnu.org; Tue, 28 Feb 2023 14:59:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pX67q-00053w-8E for bug-gnu-emacs@gnu.org; Tue, 28 Feb 2023 14:59:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pX67p-0002Lz-Qf for bug-gnu-emacs@gnu.org; Tue, 28 Feb 2023 14:59:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Stefan Monnier Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 28 Feb 2023 19:59:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61847 X-GNU-PR-Package: emacs Original-Received: via spool by 61847-submit@debbugs.gnu.org id=B61847.16776143229016 (code B ref 61847); Tue, 28 Feb 2023 19:59:01 +0000 Original-Received: (at 61847) by debbugs.gnu.org; 28 Feb 2023 19:58:42 +0000 Original-Received: from localhost ([127.0.0.1]:52057 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pX67V-0002LM-P7 for submit@debbugs.gnu.org; Tue, 28 Feb 2023 14:58:42 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:13851) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pX67U-0002LA-EN for 61847@debbugs.gnu.org; Tue, 28 Feb 2023 14:58:41 -0500 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 97BF91000BF; Tue, 28 Feb 2023 14:58:34 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id DB9B51000BD; Tue, 28 Feb 2023 14:58:32 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1677614312; bh=qSo+ywNDl4THv40oWDInuespMo7H5TwAoMTXyaKg++w=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=lxAcGiHD6SDZ4unaDvG/1kwa9jI81hcAl1eIK+Z9GX3HxJdzXFwoIIU6Bzn/E+CBs jRD+mLI8dxswSQt8zQyA93Qgsu8NvodD5bcu1F386jYgbpSfrlHcCYrAYwl+HcykVs 3HmjWH4x5ylg00zvuJfwx1D+zou/IJUGdNHEDJoMd3CK3QDV13XueZf06XBY7SufnK pEK8aYVUe+0l4nb7yb0m3n6aHIsXBsdQbhMpEXZ7OVVMCtrzRpdVbQ8GHpKmbHr4N9 oJ/oUCcJopRS+yllWbCxD79do1QbxtZcIHeNHD/sr+jQZefwS2HDCONRxWCmLHi70u Diq6RbiYFkGZg== Original-Received: from pastel (unknown [216.154.34.24]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id B0BDD120855; Tue, 28 Feb 2023 14:58:32 -0500 (EST) In-Reply-To: (Alan Mackenzie's message of "Tue, 28 Feb 2023 19:52:33 +0000") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:257010 Archived-At: >> The output for compiled functions is the main one which I think is more >> readable (among those that occur often in backtraces), so let's just >> agree to disagree on this one. > > No. The point is too important not to resolve. > > I think you're objectively wrong here. The purpose of a backtrace is > not to enter a beauty contest. Rather it's to provide the programmer > with as much information as reasonably possible to solve a bug. > > The lack of output for compiled functions with cl-prin1 condemns it. All > that appears is "#f(compiled-function)" together with an empty pair of > parentheses and a meaningless hex address. What use is any of that in > debugging a batch mode bug? > > prin1 by contrast prints the actual contents of the function - its byte > code string and its constant vector, among other things. It may not be > as "readable", but it is infinitely more useful to the person trying to > debug a bug. I'm not sure what you're expecting from me. Obviously, I'm aware of what you describe. I just don't reach the same conclusion. >> > And how will the contition-case you suggest help? (require 'cl-print nil >> > t) returns non-nil in the pertinent circumstances. >> The `noerror` argument of `require` doesn't silence the errors that >> happen while loading the file, instead it prevents signaling an error >> when the file is not found. > Whether that error is silenced or not is wholly unimportant. The only > important thing here is to get a backtrace, The silencing of the error should help to get a backtrace since it should let the code fall back to using `prin1`. Stefan