From owner-freebsd-current@FreeBSD.ORG Tue Mar 2 17:03:11 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 847CD1065674 for ; Tue, 2 Mar 2010 17:03:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 56C948FC1D for ; Tue, 2 Mar 2010 17:03:11 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id E495546B45; Tue, 2 Mar 2010 12:03:10 -0500 (EST) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 466568A01F; Tue, 2 Mar 2010 12:03:10 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 2 Mar 2010 12:03:00 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201003021203.00582.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 02 Mar 2010 12:03:10 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.5 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Mark Atkinson Subject: Re: malloc problems in -current malloc_usable_size() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2010 17:03:11 -0000 On Tuesday 02 March 2010 11:38:57 am Mark Atkinson wrote: > Hi, > > I updated my kernel/world yesterday and thunderbird 3.0.2 started core > dumping after I completed the upgrade. It continued to do so on > previously good operations after a full re-compile. > > I noticed that some jemalloc changes went in and was wondering if anyone > else was noticing SEGV problems in other apps with malloc_usable_size() > or ARENA problems in threaded apps? This may be a bug in gssapi rather than malloc(). Someone else was reporting segfaults from gss_release_buffer() because it was free()ing a bad pointer when using gssapi_krb5. -- John Baldwin