From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#23885: SEGFAULT: In procedure char-set-contains?: Wrong type argument in position 2 (expecting character): builder for libarchive-3.1.2 Date: Tue, 05 Jul 2016 09:55:28 +0200 Message-ID: <87r3b834en.fsf@gnu.org> References: <1506081467510129@web25g.yandex.ru> <20160703015818.GB1435@jasmine> <87mvlxcxzs.fsf@gnu.org> <264741467681665@web7h.yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59430) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bKLDD-0000RG-Jn for bug-guix@gnu.org; Tue, 05 Jul 2016 03:56:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bKLD8-0003xx-6q for bug-guix@gnu.org; Tue, 05 Jul 2016 03:56:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:53585) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bKLD8-0003xt-2L for bug-guix@gnu.org; Tue, 05 Jul 2016 03:56:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bKLD7-0006db-Qp for bug-guix@gnu.org; Tue, 05 Jul 2016 03:56:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <264741467681665@web7h.yandex.ru> (eus@member.fsf.org's message of "Tue, 05 Jul 2016 08:21:05 +0700") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Eus Cc: "23885@debbugs.gnu.org" <23885@debbugs.gnu.org> Eus skribis: > 04.07.2016, 20:53, "Ludovic Court=C3=A8s" : >> Leo Famulari skribis: >> >>> =C2=A0On Sun, Jul 03, 2016 at 08:42:09AM +0700, Eus wrote: >>> =C2=A0[...] >>> >>>> =C2=A0grafting '/gnu/store/7sba9q9dpkhcb2zmqcm8a00d1xrkccvz-libarchive= -3.1.2' -> '/gnu/store/ciga1934crxdimj5s1gsnvh74rk24hnd-libarchive-3.1.2'... >>>> =C2=A0grafting '/gnu/store/p07xa257vli65gx6vs3d0l3qxwqg13rk-libarchive= -3.1.2' -> '/gnu/store/ji2jgkbpl4nabwn70ax6y7kg99r7xzk7-libarchive-3.1.2'... > > [...] > >>>> =C2=A0[ 7584.270501] guile[27326]: segfault at 0 ip 00007ffff7b41c47 s= p 00007ffff4cb1930 error 4 in libguile-2.0.so.22.7.2[7ffff7a4d000+153000] >>>> =C2=A0ERROR: In procedure char-set-contains?: Wrong type argument in p= osition 2 (expecting character): builder for `/gnu/store/2fjf4zqh05lzg8sa7l= 865xvg4faqc5z4-libarchive-3.1.2.drv' failed due to signal 11 (Segmentation = fault) >> >> This is scary. Eus, is it reproducible? That is, does it happen again >> if you run: >> >> =C2=A0=C2=A0guix build --rounds=3D4 \ >> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0/gnu/store/2fjf4zqh05lzg8sa7l865xvg4faqc5z= 4-libarchive-3.1.2.drv >> >> ? > > Since I have already wiped the partition, I did everything from the begin= ning like what I have done when I encountered the segfault. This time, howe= ver, the problem did not appear. > > I see that the grafting lines that appeared before the segfault message d= iffer from the grafting lines in the successful run. In the failing one, th= ere are 29 grafting lines. In the successful one, there are 17 grafting lin= es. Moreover, the grafting of /gnu/store/ciga1934crxdimj5s1gsnvh74rk24hnd-l= ibarchive-3.1.2 and /gnu/store/ji2jgkbpl4nabwn70ax6y7kg99r7xzk7-libarchive-= 3.1.2 are reversed in the successful run although they both are still graft= ed one after another as before. > > Other than that, in the failed run, I have the following line after segfa= ult: > cannot build derivation `/gnu/store/6y3lqn4cfxsh4g87hrbmvvalip66n9hl-gril= o-0.3.0.drv': 1 dependencies couldn't be built > > In the successful run, however, ls -d /gnu/store/*-grilo-0.3.0.drv gives: > /gnu/store/cg3qlswny4242wc8f28maljd9yvwd5dd-grilo-0.3.0.drv > /gnu/store/qiwfbwn7a7cvf2lgqjlmkclwdrgl3fzz-grilo-0.3.0.drv > > Any guess as to what actually causes the segfault? > > I'd rather have you pursue this matter further, but if it is not worth th= e effort, I am okay if this report is dismissed. OK, this is weird. The segfault would be a Guile bug, something that should never happen. I=E2=80=99ve never seen it before though, so we=E2=80= =99d need more data to investigate. I=E2=80=99m closing this bug and we can reopen it when we have more info. Thanks, Ludo=E2=80=99.