From owner-freebsd-bugs@FreeBSD.ORG Fri Jul 1 15:50:11 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CBF41065672 for ; Fri, 1 Jul 2011 15:50:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1B8738FC13 for ; Fri, 1 Jul 2011 15:50:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p61FoAlx009134 for ; Fri, 1 Jul 2011 15:50:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p61FoASf009133; Fri, 1 Jul 2011 15:50:10 GMT (envelope-from gnats) Date: Fri, 1 Jul 2011 15:50:10 GMT Message-Id: <201107011550.p61FoASf009133@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: =?UTF-8?B?0JLRgdC10LLQvtC70L7QtCDQndC+0LLQuNC60L7Qsg==?= Cc: Subject: Re: kern/154073: [libz] libz causes perl to exit on signal 11 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?UTF-8?B?0JLRgdC10LLQvtC70L7QtCDQndC+0LLQuNC60L7Qsg==?= List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2011 15:50:11 -0000 The following reply was made to PR kern/154073; it has been noted by GNATS. From: =?UTF-8?B?0JLRgdC10LLQvtC70L7QtCDQndC+0LLQuNC60L7Qsg==?= To: bug-followup@FreeBSD.org, azhegalov@gmail.com Cc: Subject: Re: kern/154073: [libz] libz causes perl to exit on signal 11 Date: Fri, 01 Jul 2011 19:29:46 +0400 Hi, We have got the similar problem, seeing stack top identical, on the FreeBSD 8.2-RELEASE (amd64 arch on the 2x Intel Core Quad Xeon platform, chipset Intel 5000p). The patch provided by Andrey Zonov helps, segfaults disappear. Looks like the asm version of the longest_match() function has some bug or architecture incompatibility. The error happens not regularly, probably in very special case. We got it using PyQt to paint jam tiles basing on our data, only sometimes - after 5-30 minutes of intensive continuous painting, independently on using multi-thread features. The (pseudo)stack was always looking like: longest_match() deflate_slow() deflate() --- libpng functions --- --- Qt functions --- --- PyQt functions --- --- Python interpreter --- Regards, Vsevolod Novikov