Date: Sat, 22 Dec 2012 13:07:41 -0500 From: "Mikhail T." <mi+thun@aldan.algebra.com> To: Adrian Chadd <adrian@freebsd.org> Cc: stable@freebsd.org Subject: Re: xz(1) keeps SEGFAULT-ing Message-ID: <50D5F6ED.9050707@aldan.algebra.com> In-Reply-To: <CAJ-Vmon=CX8dHtMJmi5CY5Qzp2mx_diLqgbzMcu9D%2BaLnJgL4g@mail.gmail.com> References: <50D5CCCA.2050000@aldan.algebra.com> <CAJ-Vmon=CX8dHtMJmi5CY5Qzp2mx_diLqgbzMcu9D%2BaLnJgL4g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50D5F6ED.9050707>