Date: Sun, 20 May 2012 18:42:35 +0200 From: Alberto Villa <avilla@FreeBSD.org> To: davidxu@freebsd.org Cc: =?ISO-8859-1?Q?Gustau_P=E9rez_i_Querol?= <gperez@entel.upc.edu>, FreeBSD current <freebsd-current@freebsd.org> Subject: Re: RFC: jemalloc: qdbus sigsegv in malloc_init Message-ID: <CAJp7RHaOkEzyfD5e6pLMSBxvCBYCn9BWv=9BWu0CYsQHzGyFdg@mail.gmail.com> In-Reply-To: <4FB88925.4070008@gmail.com> References: <4F9E9E06.4070004@entel.upc.edu> <4FB88925.4070008@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, May 20, 2012 at 8:03 AM, David Xu <listlog2011@gmail.com> wrote: > qdbus segfaults on my machine too, I tracked it down, and found the probl= em > is in QT, > it deleted current_thread_data_key, =A0but it still uses it in some cxa h= ooks, > =A0I =A0applied the > following patch, =A0and it works fine. Thanks for the analysis David! > I think the bug depends on linking order in QT library ? if the > qthread_unix.cpp is linked > as lastest module, the key will be deleted after all cxa hooks run, then = it > will be fine, > otherwise, it would crash. Is this really possible? --=20 Alberto Villa, FreeBSD committer <avilla@FreeBSD.org> http://people.FreeBSD.org/~avilla
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJp7RHaOkEzyfD5e6pLMSBxvCBYCn9BWv=9BWu0CYsQHzGyFdg>