From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id Yy3dJg3my17wMgAA0tVLHw (envelope-from ) for ; Mon, 25 May 2020 15:36:45 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id WJZYIg3my15vGQAAbx9fmQ (envelope-from ) for ; Mon, 25 May 2020 15:36:45 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id F08239402D6 for ; Mon, 25 May 2020 15:36:44 +0000 (UTC) Received: from localhost ([::1]:54264 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jdF9f-00063M-Uw for larch@yhetil.org; Mon, 25 May 2020 11:36:43 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:56946) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jdEzY-0001Wn-Bb for guix-devel@gnu.org; Mon, 25 May 2020 11:26:16 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:51059) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jdEzW-0003gd-CQ; Mon, 25 May 2020 11:26:14 -0400 Received: from ti0006q161-2604.bb.online.no ([84.202.68.75]:36002 helo=localhost) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jdEzS-0007fi-Pi; Mon, 25 May 2020 11:26:12 -0400 From: Marius Bakke To: Pierre Neidhardt , Ludovic =?utf-8?Q?Court=C3=A8s?= Subject: Re: Can we increase the print width/column in daemon backtraces In-Reply-To: <87lflgjkqc.fsf@ambrevar.xyz> References: <87tvbn7ff3.fsf@ambrevar.xyz> <87k1cjihvm.fsf@elephly.net> <87h87n78yf.fsf@ambrevar.xyz> <87muf38yzh.fsf@gmail.com> <87k117x9m7.fsf@ambrevar.xyz> <87zh9xxc8b.fsf@gnu.org> <87lflgjkqc.fsf@ambrevar.xyz> Date: Mon, 25 May 2020 17:26:08 +0200 Message-ID: <87imgk6nov.fsf@gnu.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Mailman-Approved-At: Mon, 25 May 2020 11:36:30 -0400 X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: guix-devel@gnu.org, Maxim Cournoyer Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Spam-Score: -3.11 X-TUID: GbBlBmxnS4Fs --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Pierre Neidhardt writes: > Ludovic Court=C3=A8s writes: > >> Users are not supposed to see backtraces coming from the daemon or its >> helpers (=E2=80=98guix substitute=E2=80=99, =E2=80=98guix offload=E2=80= =99, etc.). > > How are we supposed to debug Guix daemon errors? You can run it directly from a shell, and/or attach a debugger. I agree that if a failure happens on the daemon level, Guix should print an actionable error message instead of a confusing back trace. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl7L45AACgkQoqBt8qM6 VPqSVwf+LvLQcns7Fc2rgHmHMeixY/3YVwgOFq0Szfm+60BXgp9bCsgiKS45TxZe D6UJeaDN52/DU9SUwTVWbwWf19NXO3EjlchLSgFzHAMcnVQFV9CVobaFCfWcskaX IeIwfGrq9u3GL3LTxxFnj0U+FrXxvNef0Rcw98AvKwoRra0bQO+CJW4TpRG+rkKo UZuYPI3YUlnTKBBU70zkZ1okP1gJSWWnNMgx9MPm6TBAOvvYI/7HmKTVpHJ8YJAj 2UuZapct9aSC1hKexHaTIpebEZUVprGtK13n49gEFt9m0shR90CG6RtJYR/NrklZ Wbs1ONbt0xNgKJqUUX8MsS24A0x4mg== =WRZl -----END PGP SIGNATURE----- --=-=-=--