From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#26497: glibc 2.25 broken on i686 Date: Fri, 14 Apr 2017 14:56:27 +0200 Message-ID: <87d1cfdu6c.fsf@gnu.org> References: <87tw5r5hxs.fsf@elephly.net> 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]:46157) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cz0mf-0005NK-Cm for bug-guix@gnu.org; Fri, 14 Apr 2017 08:57:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cz0mc-0007IB-CS for bug-guix@gnu.org; Fri, 14 Apr 2017 08:57:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:48411) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cz0mc-0007I5-9f for bug-guix@gnu.org; Fri, 14 Apr 2017 08:57:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cz0mc-0000Hq-4b for bug-guix@gnu.org; Fri, 14 Apr 2017 08:57:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87tw5r5hxs.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 14 Apr 2017 13:47:59 +0200") 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: Ricardo Wurmus Cc: 26497@debbugs.gnu.org Ricardo Wurmus skribis: > Guix on i686 is broken since the update to glibc 2.25. There are > seemingly random segfaults all over the place on my server. > > Ludo posted this upstream discussion: > > https://sourceware.org/bugzilla/show_bug.cgi?id=3D21182 Perhaps we don=E2=80=99t see the problem when running i686 code on x86_64. > I could test the patch on my i686 system, but it would take much too > long for me to build the system from source on my machines. Could you first check if there=E2=80=99s a simple way to reproduce it on yo= ur machine? For example, run =E2=80=9Cguix build coreutils=E2=80=9D or =E2=80= =9Cguix build coreutils --check=E2=80=9D and see if that fails. If it does, you could arrange to test the patch just in this setup. Thanks, Ludo=E2=80=99.