Date: Fri, 11 May 2018 18:44:03 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 220767] lang/beignet: hangs if consumer is not linked against libpthread after jemalloc 5.0.0 update Message-ID: <bug-220767-7141-V3FRmtT5MS@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220767-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-220767-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220767 --- Comment #6 from Jason Evans <jasone@FreeBSD.org> --- I don't have any specific ideas as to why this is happening. Bootstrapping jemalloc on FreeBSD is really tricky, because pthreads mutexes use malloc, and jemalloc has to jump through hoops to initialize its mutexes in multiple phases. It looks like beignet depends on the libpthread-stubs package. Is it possible that the stubs don't sufficiently stub out the libc-internal hooks that jemalloc uses to bootstrap? Here's a list of pthreads-related symbols jemalloc depends on (generated by building stand-alone jemalloc): _pthread_mutex_init_calloc_cb je_pthread_create_wrapper pthread_cond_init pthread_cond_signal pthread_cond_timedwait pthread_cond_wait pthread_create pthread_create_fptr pthread_join pthread_mutex_lock pthread_mutex_trylock pthread_mutex_unlock pthread_sigmask -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220767-7141-V3FRmtT5MS>