all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Roel Janssen <roel@gnu.org>
To: Paul van der Walt <paul@denknerd.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Everything segfaults
Date: Thu, 09 Jun 2016 17:11:13 +0200	[thread overview]
Message-ID: <87a8iujt2m.fsf@gnu.org> (raw)
In-Reply-To: <87h9d22z82.fsf@Cage.localdomain>


Paul van der Walt writes:

> Hello Guix,
>
> It's been a while, so i apologise for asking what are probably dumb
> questions.
>
> Quite a while ago i ran into this issue where (it might have been after
> a system upgrade including libc and such, i'm using git Guix on Arch
> Linux) all binaries segfault.

From what kernel version, to what kernel version have you moved?

> I didn't really have time to look at it then, and now i'm trying to get
> back on the Guix-horse.  I've done `guix package -i ..` for a few
> packages, some of which have and some of which haven't been updated in
> the meantime, but the problem persists.  Should i blow away the entire
> /gnu/store and reinstall Guix from scratch, or can something be
> debugged/salvaged?  My debugging-fu is weak, so i might need pointers.

Could you try running a program from your Guix profile using strace?
So, running it as normal, but then prepend "strace", like:
  strace git log

It may help figuring out what goes wrong.

Maybe this question belongs to help-guix@gnu.org instead.

Kind regards,
Roel Janssen

  reply	other threads:[~2016-06-09 15:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 14:50 Everything segfaults Paul van der Walt
2016-06-09 15:11 ` Roel Janssen [this message]
2016-06-09 15:14   ` Paul van der Walt
  -- strict thread matches above, loose matches on Subject: below --
2016-06-09 15:20 Paul van der Walt
2016-06-09 17:28 ` Andreas Enge
2016-06-14 18:30   ` Paul van der Walt
2016-06-14 21:46     ` Ludovic Courtès
2016-06-14 22:27       ` Paul van der Walt
2016-06-15 11:24         ` 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=87a8iujt2m.fsf@gnu.org \
    --to=roel@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=paul@denknerd.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 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.