From owner-freebsd-perl@FreeBSD.ORG Tue Mar 11 15:12:14 2008 Return-Path: Delivered-To: freebsd-perl@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 253AE1065674 for ; Tue, 11 Mar 2008 15:12:14 +0000 (UTC) (envelope-from tobez@tobez.org) Received: from heechee.tobez.org (heechee.tobez.org [194.255.56.42]) by mx1.freebsd.org (Postfix) with ESMTP id 81FF08FC17 for ; Tue, 11 Mar 2008 15:12:13 +0000 (UTC) (envelope-from tobez@tobez.org) Received: by heechee.tobez.org (Postfix, from userid 1001) id B0F926D412; Tue, 11 Mar 2008 15:55:55 +0100 (CET) Date: Tue, 11 Mar 2008 15:55:55 +0100 From: Anton Berezin To: Jeremy Messenger Message-ID: <20080311145555.GK53444@heechee.tobez.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Powered-By: FreeBSD http://www.freebsd.org/ User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-perl@freebsd.org Subject: Re: Perl malloc doesn't work in FreeBSD 7.x with xchat anymore. X-BeenThere: freebsd-perl@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: maintainer of a number of perl-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Mar 2008 15:12:14 -0000 On Sat, Mar 08, 2008 at 04:43:55PM -0600, Jeremy Messenger wrote: > Hello folks, > > See here: http://www.freebsd.org/cgi/query-pr.cgi?pr=121472 > Backtraces: http://people.freebsd.org/~mezz/gdb/gdb-xchat.txt > > It works ok in FreeBSD 6.x, but not FreeBSD 7.x. If I reinstall perl5.8 > with WITHOUT_PERL_MALLOC and it solves the problem of xchat with perl > plugins crash in FreeBSD 7.x. I have no idea where I am supposed to look > at. Do anyone know if this issue will be fixed in Perl 5.10? I do not believe it is a Perl issue at all. It is indicated by the backtrace that Perl malloc's service areas are corrupted. I can think of two possibilities: - a problem of malloc'ed memory ownership (when it is allocated with one malloc implementation and free'd with another one); - a genuine memory corruption within xchat which goes unnoticed on 6.x with phkmalloc and manifests itself on 7.x with jemalloc. I seem to have a rather vague recollection that something similar has happened with xchat before (some years ago). One more possibility is that xchat is threaded and Perl is not. Cheers, \Anton. -- We're going for 'working' here. 'clean' is for people with skills... -- Flemming Jacobsen