Date: Mon, 31 Aug 2015 16:29:36 -0400 From: Ed Maste <emaste@freebsd.org> To: Julien Grall <julien.grall@citrix.com> Cc: freebsd-arm <freebsd-arm@freebsd.org>, Andrew Turner <andrew@freebsd.org> Subject: Re: arm64: userspace broken with jemalloc 4.0.0 Message-ID: <CAPyFy2AQy0ze4q4U=F5ZD%2BRJ8fvxck-0oHEJEoS8mP_gA5XX4w@mail.gmail.com> In-Reply-To: <55E381F5.1030107@citrix.com> References: <55E22CC0.9000306@citrix.com> <52BA8254-5B14-45BC-A434-3DE3E2A9F37B@canonware.com> <55E2FC47.5070801@citrix.com> <55E381F5.1030107@citrix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30 August 2015 at 18:21, Julien Grall <julien.grall@citrix.com> wrote: > > > So I figured out the problem today. ls is linked to 2 libraries using local > thread storage: libxo and libc. Somehow the 2 libraries are using the same > base pointer for the storage. > > When libxo will try to realloc a pointer living in the thread storage, > jemalloc will throw an exception (the ASSERT mentioned earlier) because the > pointer is invalid. The pointer was expected to be NULL but it has been > overwritten by jemalloc earlier. Would you submit a PR for this to keep track of it while the investigation is ongoing?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2AQy0ze4q4U=F5ZD%2BRJ8fvxck-0oHEJEoS8mP_gA5XX4w>