From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: Artyom Poptsov <poptsov.artyom@gmail.com>, 26976@debbugs.gnu.org
Subject: bug#26976: On Hydra, offload crashes while trying to build linux-libre source
Date: Sat, 20 May 2017 00:36:46 +0200 [thread overview]
Message-ID: <87mva88oe9.fsf@gnu.org> (raw)
In-Reply-To: <87pof5dnja.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 19 May 2017 14:44:09 +0200")
Hi again,
I was able to reproduce it on hydra.gnu.org with:
guix copy --to=hydra.gnunet.org /gnu/store/gi7r1v65zqhh8riqprq8nchfc9v9k156-guix-current
which leads most of the time to SIGSEGV (I couldn’t get the SIGSEGV on
my laptop):
--8<---------------cut here---------------start------------->8---
Thread 1 received signal SIGSEGV, Segmentation fault.
0x00007f121ff61ac7 in deflate_fast () from /gnu/store/jwkcd7siv6fcyl0qsg607bg9c8ap0gqr-zlib-1.2.11/lib/libz.so.1
(gdb) bt
#0 0x00007f121ff61ac7 in deflate_fast () from /gnu/store/jwkcd7siv6fcyl0qsg607bg9c8ap0gqr-zlib-1.2.11/lib/libz.so.1
#1 0x00007f121ff6378d in deflate () from /gnu/store/jwkcd7siv6fcyl0qsg607bg9c8ap0gqr-zlib-1.2.11/lib/libz.so.1
#2 0x00007f121e281451 in gzip_compress () from /gnu/store/vlc43y485v80sgq7iw60hzy4pw5r52d2-libssh-0.7.4/lib/libssh.so.4
#3 0x00007f121e281783 in compress_buffer () from /gnu/store/vlc43y485v80sgq7iw60hzy4pw5r52d2-libssh-0.7.4/lib/libssh.so.4
#4 0x00007f121e266ea7 in packet_send2 () from /gnu/store/vlc43y485v80sgq7iw60hzy4pw5r52d2-libssh-0.7.4/lib/libssh.so.4
#5 0x00007f121e257598 in channel_write_common () from /gnu/store/vlc43y485v80sgq7iw60hzy4pw5r52d2-libssh-0.7.4/lib/libssh.so.4
#6 0x00007f121e6c15ee in write_to_channel_port () from /gnu/store/ql5h9hxh5560d42xdirh0yxzrgii6i0m-guile-ssh-0.11.0/lib/libguile-ssh.so.11
#7 0x00007f122532472c in scm_i_write_bytes () from /gnu/store/5zx29y44nrqj0s8h3jlvlj82k8hj4dxs-guile-2.2.2/lib/libguile-2.2.so.1
#8 0x00007f122532bde4 in scm_put_bytevector () from /gnu/store/5zx29y44nrqj0s8h3jlvlj82k8hj4dxs-guile-2.2.2/lib/libguile-2.2.so.1
#9 0x00007f1225360c4d in vm_regular_engine () from /gnu/store/5zx29y44nrqj0s8h3jlvlj82k8hj4dxs-guile-2.2.2/lib/libguile-2.2.so.1
--8<---------------cut here---------------end--------------->8---
Unfortunately, when running under “valgrind --trace-children=yes”, it
doesn’t segfault and Valgrind doesn’t report anything interesting
(neither on hydra.gnu.org nor on my laptop).
I built libssh and guile-ssh with -fsanitize=address on my laptop but
that doesn’t report anything useful either.
Suggestions welcome!
Ludo’.
next prev parent reply other threads:[~2017-05-19 22:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 1:55 bug#26976: On Hydra, offload crashes while trying to build linux-libre source Mark H Weaver
2017-05-18 2:02 ` Mark H Weaver
2017-05-18 22:00 ` Ludovic Courtès
2017-05-19 3:20 ` Artyom Poptsov
2017-05-19 12:44 ` Ludovic Courtès
2017-05-19 22:36 ` Ludovic Courtès [this message]
2017-05-20 21:59 ` Ludovic Courtès
2017-06-05 21:33 ` Ludovic Courtès
2017-06-13 21:32 ` Ludovic Courtès
2017-06-14 20:10 ` Ludovic Courtès
2017-07-27 10:14 ` Ludovic Courtès
2017-05-20 16:59 ` Mark H Weaver
2017-05-20 18:02 ` Ludovic Courtès
2017-05-20 22:21 ` Ludovic Courtès
2017-06-14 6:58 ` Mark H Weaver
2017-06-14 7:15 ` Mark H Weaver
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=87mva88oe9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=26976@debbugs.gnu.org \
--cc=mhw@netris.org \
--cc=poptsov.artyom@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 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).