From owner-freebsd-current@FreeBSD.ORG Tue Mar 2 17:21:46 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 F0257106564A for ; Tue, 2 Mar 2010 17:21:46 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id A91D48FC15 for ; Tue, 2 Mar 2010 17:21:46 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1NmVmz-0006wu-Az for freebsd-current@freebsd.org; Tue, 02 Mar 2010 18:21:45 +0100 Received: from 207.155.204.151.ptr.us.xo.net ([207.155.204.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Mar 2010 18:21:45 +0100 Received: from atkin901 by 207.155.204.151.ptr.us.xo.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Mar 2010 18:21:45 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Mark Atkinson Date: Tue, 02 Mar 2010 09:21:27 -0800 Lines: 21 Message-ID: References: <201003021203.00582.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 207.155.204.151.ptr.us.xo.net User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.8) Gecko/20100301 Thunderbird/3.0.2 In-Reply-To: <201003021203.00582.jhb@freebsd.org> 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:21:47 -0000 On 03/02/10 09:03, John Baldwin wrote: > 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. > Thanks for that tip, I didn't associated that with the LDAP thread until now. LD_PRELOAD ing a dummy gss_release_buffer() stops the segfaulting. Curious it only showed up after I updated. I had an Jan 11th kernel/world earlier.