From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Bj=C3=B6rn_?= =?UTF-8?Q?H=C3=B6fling?= Subject: bug#36471: Unreadable Stacktrace Example Date: Tue, 2 Jul 2019 13:12:45 +0200 Message-ID: <20190702131245.15561fbd@alma-ubu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/9k.S3lxhkcQeyY1FXHhzMez"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:55348) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hiGie-0005Wj-7b for bug-guix@gnu.org; Tue, 02 Jul 2019 07:13:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hiGic-00078J-Tb for bug-guix@gnu.org; Tue, 02 Jul 2019 07:13:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:37784) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hiGic-00077Z-Q6 for bug-guix@gnu.org; Tue, 02 Jul 2019 07:13:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Received: from eggs.gnu.org ([2001:470:142:3::10]:55312) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hiGiS-0005KW-2n for bug-guix@gnu.org; Tue, 02 Jul 2019 07:12:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hiGiQ-0006eo-0u for bug-guix@gnu.org; Tue, 02 Jul 2019 07:12:51 -0400 Received: from m4s11.vlinux.de ([83.151.27.109]:54220 helo=bjoernhoefling.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hiGiP-0006ZO-Lq for bug-guix@gnu.org; Tue, 02 Jul 2019 07:12:49 -0400 Received: from alma-ubu (pD951F287.dip0.t-ipconnect.de [217.81.242.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bjoernhoefling.de (Postfix) with ESMTPSA id DA2B93F945 for ; Tue, 2 Jul 2019 13:12:45 +0200 (CEST) List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 36471@debbugs.gnu.org Cc: robert vollmert --Sig_/9k.S3lxhkcQeyY1FXHhzMez Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Debbugs-CC: Robert Vollmert Hello, in the 1.0-beyond-discussions, Robert asked that Stacktraces should be more clear. I refer to this message (lists.gnu.org is down, so I cannot link): From: Ludovic Court=C3=A8s To: Robert Vollmert Subject: Re: Guix beyond 1.0: let=E2=80=99s have a roadmap! Message-ID: <878stirsdc.fsf@gnu.org> Here is my example. I'm on top of 48eb71aea807262210c38b5fb675d747adfccff3 First the full stacktrace, below are some comments: ./pre-inst-env guix lint -c cve freecad =20 Backtrace:reecad@0.18.2-1.dbb4cc6 [cve]... 11 (apply-smob/1 #) In ice-9/boot-9.scm: 705:2 10 (call-with-prompt _ _ #) In ice-9/eval.scm: 619:8 9 (_ #(#(#))) In guix/ui.scm: 1668:12 8 (run-guix-command _ . _) In srfi/srfi-1.scm: 640:9 7 (for-each # ?) In guix/scripts/lint.scm: 1152:4 6 (run-checkers # ?) In srfi/srfi-1.scm: 640:9 5 (for-each # ?) In guix/scripts/lint.scm: 933:4 4 (check-vulnerabilities _) 928:9 3 (_ _) In unknown file: 2 (force #) In guix/scripts/lint.scm: 917:24 1 (_) In ice-9/boot-9.scm: 829:9 0 (catch srfi-34 # ?) ice-9/boot-9.scm:829:9: In procedure catch: In procedure connect: Connection timed out OK, this is semi-readable but I will explain a bit what I find strange/unreadable: In guix/scripts/lint.scm: 1152:4 6 (run-checkers # ?) --> OK: This is perfectly readable. I know in which procedure I am, in which line, the line matches my source code. Fine. In srfi/srfi-1.scm: 640:9 5 (for-each # ?) --> This is OK, though it could print the line of the procedure? In guix/scripts/lint.scm: 933:4 4 (check-vulnerabilities _) 928:9 3 (_ _) --> 933: Nice, I'm in check-vulnerabilities. But why is there no argument? --> What is this strange second line: (_ _)? Why is there nothing written? Is that due to tail-recursion? In unknown file: 2 (force #) --> Why is this in a "unknown file"? --> Is this force/promise making my stacktrace more unreadable? In guix/scripts/lint.scm: 917:24 1 (_) --> Uh. Any more details?. Is "(_)" the call to "(current-vulnerabilities*)= "?! In ice-9/boot-9.scm: 829:9 0 (catch srfi-34 # ?) ice-9/boot-9.scm:829:9: In procedure catch: In procedure connect: Connection timed out --> Now, wait: The real problem happens somewhere down here and I don't have any detailed stacktrace about that? I have to manually go down into current-vulnerabilities*, call/nw/failsaife, etc? Why don't I get the details from here? Is this because in "call-with-networking-fail-safe", line 900 we through newly: (args (apply throw args)))))) but then the stacktrace gets lost? Would there be a throw-with-caused-by? Bj=C3=B6rn --Sig_/9k.S3lxhkcQeyY1FXHhzMez Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQiGUP0np8nb5SZM4K/KGy2WT5f/QUCXRs8LQAKCRC/KGy2WT5f /WriAKCOjwhhYoGSxGKHLZhpIMWYP4RKpwCeNjzYVT/jZBRvR+uty6irzLjYzKw= =DeJN -----END PGP SIGNATURE----- --Sig_/9k.S3lxhkcQeyY1FXHhzMez--