From: Maxime Devos <maximedevos@telenet.be>
To: Mathieu Othacehe <othacehe@gnu.org>, 53142@debbugs.gnu.org
Subject: bug#53142: cuirass: useless guile backtraces.
Date: Sun, 09 Jan 2022 16:11:55 +0000 [thread overview]
Message-ID: <46f6c732e4718836f789ffbc696bf2512268150d.camel@telenet.be> (raw)
In-Reply-To: <87k0f8kilu.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
Mathieu Othacehe schreef op zo 09-01-2022 om 16:57 [+0100]:
> 64325600:In ice-9/eval.scm:
> 64325601- 619:8 2 (_ #(#(#<directory (cuirass scripts remote-server) ?> ?)))
> 64325602- 619:8 1 (_ #(#(#(#(#(#(#<directory (cuirass scr?> ?)) ?) ?) ?) ?))
> 64325603:In ice-9/boot-9.scm:
> 64325604- 1685:16 0 (raise-exception _ #:continuable? _)
> 64325605-2022-01-09T11:03:44 debug: 141.80.167.161 (gnijzoxQ): no available build.
> 64325606:ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> 64325607:In procedure struct-vtable: Wrong type argument in position 1 (expecting struct): #f
> --8<---------------cut here---------------end--------------->8---
>
> Any idea how to make those backtraces more helpful?
Set COLUMNS=9000, then Guile stop trying to fit them in 80 columns,
it will try 9000 columns instead.
Also, backtraces are clearer for compiled code (avoiding (ice-9 eval)).
Is (cuirass scripts remote-server) compiled to .go?
There's might be guile variable you could set as well (or an argument
to 'backtrace'?), but I forgot the details.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-01-09 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 15:57 bug#53142: cuirass: useless guile backtraces Mathieu Othacehe
2022-01-09 16:11 ` Maxime Devos [this message]
2022-01-10 8:17 ` Mathieu Othacehe
2022-01-19 9:46 ` Mathieu Othacehe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46f6c732e4718836f789ffbc696bf2512268150d.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53142@debbugs.gnu.org \
--cc=othacehe@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).