From owner-freebsd-stable@FreeBSD.ORG Sat Dec 22 18:07:43 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8A752269; Sat, 22 Dec 2012 18:07:43 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 24F188FC12; Sat, 22 Dec 2012 18:07:42 +0000 (UTC) Received: from mr16.lnh.mail.rcn.net ([207.172.157.36]) by smtp02.lnh.mail.rcn.net with ESMTP; 22 Dec 2012 13:07:42 -0500 Received: from smtp04.lnh.mail.rcn.net (smtp04.lnh.mail.rcn.net [207.172.157.104]) by mr16.lnh.mail.rcn.net (MOS 4.3.4-GA) with ESMTP id CDP34317; Sat, 22 Dec 2012 13:07:41 -0500 X-Auth-ID: anat Received: from pool-173-70-92-11.nwrknj.fios.verizon.net (HELO [192.168.1.8]) ([173.70.92.11]) by smtp04.lnh.mail.rcn.net with ESMTP; 22 Dec 2012 13:07:41 -0500 Message-ID: <50D5F6ED.9050707@aldan.algebra.com> Date: Sat, 22 Dec 2012 13:07:41 -0500 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120820 Thunderbird/14.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: xz(1) keeps SEGFAULT-ing References: <50D5CCCA.2050000@aldan.algebra.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2012 18:07:43 -0000 On 22.12.2012 11:39, Adrian Chadd wrote: > Is it dumping core? Yes, and, as I type this, I'm trying to reproduce the crash using the version of liblzma.so.5 compiled with "-O0 -g" (under valgrind). So far (25%) everything is clean and valgrind has no complaints either. Yours, -mi >> Following xz's fault, all other processes (dump, ccrypt, sh) dump their >> cores to, but, according to dmesg, the culprit is always xz.*According to >> core, the fault is somewhere inside liblzma.so.5*. I recompiled the library >> to enable debugging and am trying to investigate, but, perhaps, someone has >> already run into this?