all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: "Nicolò Balzarotti" <anothersms@gmail.com>
Cc: 47761@debbugs.gnu.org
Subject: bug#47761: Guile Segfaulting on guix build -f
Date: Wed, 14 Apr 2021 00:33:58 +0200	[thread overview]
Message-ID: <20210414003358.54fa9c37@tachikoma.lepiller.eu> (raw)
In-Reply-To: <87im4pooif.fsf@guixSD.i-did-not-set--mail-host-address--so-tickle-me>

Le Tue, 13 Apr 2021 23:36:40 +0200,
Nicolò Balzarotti <anothersms@gmail.com> a écrit :

> Hi guix!
> 
> A package definition that used to build fine, recently (don't know
> exactly when) started failing, with guile segfaulting.
> 
> After removing a few things, it seems that the MWE is this:
> 
> echo '(use-modules (guix git-download)) (git-predicate "repo")'>m.scm
> mkdir repo
> guix build -f m.scm
> Segmentation fault
> 
> guix describe:
> 
> guix 2a62425
>    repository URL: https://git.savannah.gnu.org/git/guix.git
>    branch: master
>    commit: 2a624253bc55e2a94f6581d6e790303575436c96
> 
> One of the two computers provides substitute to the other, so maybe my
> guile is somehow damaged?  Can any of you reproduce it?
> 
> Thanks, Nicolò
> 
> 
> 

I can reproduce the segfault when "repo" is a directory that exists
(seems to be independent from content, I can reproduce with an empty
directory and an actually git repository), from guix repl:

scheme@(guix-user)> (use-modules (guix git-download))
scheme@(guix-user)> (git-predicate "repo")
Erreur de segmentation




  parent reply	other threads:[~2021-04-13 22:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-13 21:36 bug#47761: Guile Segfaulting on guix build -f Nicolò Balzarotti
2021-04-13 21:52 ` Nicolò Balzarotti
2021-04-13 22:33 ` Julien Lepiller [this message]
2021-04-13 22:54 ` Leo Prikler
2021-04-18 10:22 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210414003358.54fa9c37@tachikoma.lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=47761@debbugs.gnu.org \
    --cc=anothersms@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.