From: elaexuotee--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 53296@debbugs.gnu.org
Subject: bug#53296: Intermittent segfaults when parsing (?) custom package from repo.
Date: Sun, 12 Feb 2023 22:07:52 +0900 [thread overview]
Message-ID: <2FC0U30KGWBVR.2IVXS2127QF0U@wilsonb.com> (raw)
In-Reply-To: <87o82g96i7.fsf@gnu.org>
Nothing like ACKing a year later!
This was almost certainly a local hardware issue. The machine this happened on
ended up showing progressively more mysterious behaviour that could not be
reproduced on other machines.
Feel free to close!
Ludovic Courtès <ludo@gnu.org> wrote:
> Hi,
>
> Any update on this one?
>
> https://issues.guix.gnu.org/53296
>
> If there’s no reliable way to reproduce it, I’ll close the bug soon.
>
> Thanks,
> Ludo’.
>
> Ludovic Courtès <ludo@gnu.org> skribis:
>
> > 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’.
next prev parent reply other threads:[~2023-02-12 13:09 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
2022-03-08 8:46 ` Ludovic Courtès
2023-02-12 13:07 ` elaexuotee--- via Bug reports for GNU Guix [this message]
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
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=2FC0U30KGWBVR.2IVXS2127QF0U@wilsonb.com \
--to=bug-guix@gnu.org \
--cc=53296@debbugs.gnu.org \
--cc=elaexuotee@wilsonb.com \
--cc=ludo@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).