From: o.rojon@posteo.net
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 41715@debbugs.gnu.org
Subject: bug#41715: The program '/gnu/store/foobar/compute-guix-derivation' failed to compute the derivation for guix
Date: Fri, 12 Jun 2020 07:54:32 +0200 [thread overview]
Message-ID: <47c4e596596303893a847212ffa4da9b@posteo.net> (raw)
In-Reply-To: <87mu5cia64.fsf@gnu.org>
Hej Ludo,
crazy, I wouldn't have thought it would go as deep as gdb as quickly ;-)
I followed the steps you mentioned, the results you find here:
https://www.mediafire.com/file/g5yz8f3pput8f3w/gdb-output/file . The
only part I omitted from the gdb output is the first lines mentioned the
license. (Will look at IPFS, maybe next time :))
If you need anything else, dont hesitate to specify. Also, should a
reinstall become necessary, that would be annoying but not the end of
the world. So if we hit a dead end thats fine by me.
Thanks a lot for your help. So far, I received only good from the guix
community :)
Greetings,
Olivier
On 09.06.2020 16:30, Ludovic Courtès wrote:
> Hi,
>
> o.rojon@posteo.net skribis:
>
>> here is the log uploaded on mediafire:
>> http://www.mediafire.com/file/ldqoi68y88rzrn9/log.bz2/file (note that
>> if you can recommend another uploading service, feel free to!)
>
> I don’t know, maybe you could run IPFS.
>
> The log reads:
>
> --8<---------------cut here---------------start------------->8---
> clone(child_stack=NULL,
> flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
> child_tidptr=0x7f3d44cfee50) = 1498
> close(17) = 0
> read(16, "", 1) = 0
> close(16) = 0
> wait4(1498, [{WIFSIGNALED(s) && WTERMSIG(s) == SIGBUS}], 0, NULL) =
> 1498
> --8<---------------cut here---------------end--------------->8---
>
> … which means the ‘compute-guix-derivation’ process crashed with
> SIGBUS.
>
> Could you run:
>
> ulimit -c unlimited
> guix pull
>
> That should fail again, but this time there should be a ‘core’ file in
> the current directory (or ‘core.’ followed by digits).
>
> Then you can run:
>
> gdb --core=./core
>
> and at the GDB prompt, type:
>
> thread apply all bt
>
> Could you let me know what that returns?
>
> Thanks,
> Ludo’.
next prev parent reply other threads:[~2020-06-12 5:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 19:12 bug#41715: The program '/gnu/store/foobar/compute-guix-derivation' failed to compute the derivation for guix o.rojon
2020-06-04 20:00 ` Ludovic Courtès
2020-06-05 5:54 ` o.rojon
2020-06-05 8:26 ` o.rojon
2020-06-05 16:29 ` Ludovic Courtès
2020-06-06 0:57 ` o.rojon
2020-06-07 19:47 ` Ludovic Courtès
2020-06-08 14:55 ` o.rojon
2020-06-09 14:30 ` Ludovic Courtès
2020-06-12 5:54 ` o.rojon [this message]
2020-06-12 14:12 ` Ludovic Courtès
2020-07-21 18:11 ` Olivier
2020-07-22 10:12 ` Ludovic Courtès
2020-06-04 22:15 ` Jakub Kądziołka
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=47c4e596596303893a847212ffa4da9b@posteo.net \
--to=o.rojon@posteo.net \
--cc=41715@debbugs.gnu.org \
--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).