Date: Tue, 1 Sep 2015 11:52:57 +0100 From: Julien Grall <julien.grall@citrix.com> To: Ed Maste <emaste@freebsd.org> Cc: Andrew Turner <andrew@freebsd.org>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: arm64: userspace broken with jemalloc 4.0.0 Message-ID: <55E58389.5040606@citrix.com> In-Reply-To: <CAPyFy2AQy0ze4q4U=F5ZD%2BRJ8fvxck-0oHEJEoS8mP_gA5XX4w@mail.gmail.com> References: <55E22CC0.9000306@citrix.com> <52BA8254-5B14-45BC-A434-3DE3E2A9F37B@canonware.com> <55E2FC47.5070801@citrix.com> <55E381F5.1030107@citrix.com> <CAPyFy2AQy0ze4q4U=F5ZD%2BRJ8fvxck-0oHEJEoS8mP_gA5XX4w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Ed, On 31/08/15 21:29, Ed Maste wrote: > 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? Andrew provides a patch to fix the problem on the thread. Let me know if it's still worth to submit a PR. Regards, -- Julien Grall
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55E58389.5040606>