Date: Wed, 17 Mar 2010 08:05:50 -0700 From: Mark Atkinson <atkin901@gmail.com> To: freebsd-current@freebsd.org Subject: Re: malloc problems in -current malloc_usable_size() Message-ID: <hnqr4e$hd$1@dough.gmane.org> In-Reply-To: <hmjheo$ckn$1@dough.gmane.org> References: <hmjev2$qhm$1@dough.gmane.org> <201003021203.00582.jhb@freebsd.org> <hmjheo$ckn$1@dough.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/02/10 09:21, Mark Atkinson wrote: > 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. Just a quick note, I found that using sasl 2 will also avoid the problem cyrus-sasl-2.1.23 RFC 2222 SASL (Simple Authentication and Security Layer) LD_PRELOAD=/usr/local/lib/sasl2/libgssapiv2.so.2 thunderbird
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?hnqr4e$hd$1>