From: "Ludovic Courtès" <ludo@gnu.org>
To: 39266@debbugs.gnu.org
Subject: bug#39266: Finalization thread hits wrong-type-arg on weak vector (AArch64)
Date: Wed, 19 Feb 2020 14:50:51 +0100 [thread overview]
Message-ID: <87k14in0sk.fsf@gnu.org> (raw)
In-Reply-To: <87tv4kdgyy.fsf@inria.fr> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22\?\= \=\?utf-8\?Q\?'s\?\= message of "Fri, 24 Jan 2020 16:14:29 +0100")
Ludovic Courtès <ludo@gnu.org> skribis:
> While building the “guix-system.drv” derivation on AArch64, I got this
> crash (not fully deterministic but quite frequent). Here the
> finalization thread gets a wrong-type-arg in ‘scm_i_weak_car’ (i.e.,
> accessing a one-element weak vector):
>
> $ ( export out=$PWD/build; unset GUILE_LOAD_PATH; unset GUILE_LOAD_COMPILED_PATH; gdb --args "/gnu/store/p8in2npgl5yhliy25ikz7shjbq0gii95-guile-next-3.0.0/bin/guile" "--no-auto-compile" "-L" "/gnu/store/3qg8l6kr4wa9sbgwy00z1mb3p88xf455-module-import" "-C" "/gnu/store/h9qcvg71bmx735fsndagll9y7s72k9n9-module-import-compiled" guix-system-builder )
> […]
> loading 'gnu/services/cups.scm'...
> Backtrace:
Apparently this bug does not occur with v3.0.0-23-g7dc90a17e¹. It may
be that 00fbdfa7345765168e14438eed0b0b8c64c27ab9 reduces GC pressure,
which as a side effect makes the problem vanish.
It’s not satisfactory, but as a stop-gap measure, we could release 3.0.1
like this, which could make Guile 3 usable for Guix on AArch64.
Thoughts?
Ludo’.
¹ Specifically, I tested by (1) building a tarball with “make dist”, (2)
running “guix build guile-next
--with-source=guile-next=the-tarball.tar.gz”, and (3) running that
Guile in the code above. For some reason, Guile 3.0.0 built “by hand”
would not reproduce the original bug, which is why I built it through
Guix.
next prev parent reply other threads:[~2020-02-19 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 15:14 bug#39266: Finalization thread hits wrong-type-arg on weak vector (AArch64) Ludovic Courtès
2020-02-19 13:50 ` Ludovic Courtès [this message]
2020-02-19 14:19 ` Brian Woodcox
2020-02-29 15:09 ` shtwzrd via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2020-03-09 14:38 ` Ludovic Courtès
2020-03-09 22:19 ` Pierre Langlois
2020-03-10 17:25 ` Ludovic Courtès
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k14in0sk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=39266@debbugs.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.
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).