Date: Fri, 04 Aug 2006 12:55:46 -0700 From: Jason Evans <jasone@FreeBSD.org> To: Peter Grehan <peterg@ptree32.com.au> Cc: Maxim Sobolev <sobomax@FreeBSD.org>, "current@freebsd.org" <current@FreeBSD.org>, Peter Grehan <grehan@FreeBSD.org>, Steve Kargl <sgk@troutmask.apl.washington.edu>, freebsd-ppc@FreeBSD.org Subject: Re: Looks like threading is b0rken on FreeBSD/powerpc Message-ID: <44D3A642.1000905@FreeBSD.org> In-Reply-To: <44D1757D.4010103@ptree32.com.au> References: <44D12AC0.90009@sippysoft.com> <20060802230803.GA32778@troutmask.apl.washington.edu> <44D13BC7.8010309@FreeBSD.org> <44D168A8.1060201@freebsd.org> <44D173B7.6040302@FreeBSD.org> <44D1757D.4010103@ptree32.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Grehan wrote: >> But libpthread works in 6.0. What's the difference? > > jemalloc. From the backtrace, t's doing a TLS allocation, where I'm > certain phkmalloc didn't do anything like that. Indeed, jemalloc does add a dependency on TLS for PIC versions, though it can be configured to run (more slowly) without TLS, as Marcel pointed out. This appears to be a bug in the TLS implementation, rather than in jemalloc; the appropriate fix is to make TLS work. Jason
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44D3A642.1000905>