all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: elaexuotee@wilsonb.com
Cc: 53296@debbugs.gnu.org
Subject: bug#53296: Intermittent segfaults when parsing (?) custom package from repo.
Date: Tue, 18 Jan 2022 12:28:57 +0100	[thread overview]
Message-ID: <87ee55jn9i.fsf@gnu.org> (raw)
In-Reply-To: <3GNCGE6R9I4MM.3JY1C8V1IN7CY@wilsonb.com> (elaexuotee@wilsonb.com's message of "Tue, 18 Jan 2022 15:23:40 +0900")

Hi,

elaexuotee@wilsonb.com skribis:

> Ludovic Courtès <ludo@gnu.org> wrote:
>> Here’s how I tried (and failed) to reproduce the segfault:
>> 
>> --8<---------------cut here---------------start------------->8---
>> $ find /tmp/test
>> /tmp/test
>> /tmp/test/gnu
>> /tmp/test/gnu/packages
>> /tmp/test/gnu/packages/jsoftware.scm
>> 
>> $ guix build -L /tmp/test jsoftware
>> /tmp/test/gnu/packages/jsoftware.scm:76:0: warning: source expression failed to match any pattern
>> guix build: error: jsoftware: nekonata pako
>
> Is that an Esperanto locale?!

Jes!

> The segfault is pretty inconsistent on my end. Unfortunately, the only
> "reliable" way to produce I know at the moment is to badger the build command
> repeatedly and get (un)lucky.

OK, please let us know when you have a reliable reproducer, or GDB
backtraces, things like that.

Thanks,
Ludo’.




  reply	other threads:[~2022-01-18 11:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-16  6:12 bug#53296: Intermittent segfaults when parsing (?) custom package from repo elaexuotee--- via Bug reports for GNU Guix
2022-01-17 15:42 ` Ludovic Courtès
2022-01-18  6:23   ` elaexuotee--- via Bug reports for GNU Guix
2022-01-18 11:28     ` Ludovic Courtès [this message]
2022-03-08  8:46       ` Ludovic Courtès
2023-02-12 13:07         ` elaexuotee--- via Bug reports for GNU Guix
2023-02-14 12:04           ` Simon Tournier

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=87ee55jn9i.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=53296@debbugs.gnu.org \
    --cc=elaexuotee@wilsonb.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.