On Tue, Jan 20, 2015 at 08:55:05AM +0000, Poul-Henning Kamp wrote: > I just tried current as of yesterday and had to give up rather quickly. > > unbound sig#11'ed on bootup, couldn't find a coredump. > > Trying to read a PDF file with evince I got one: > > $ evince > Fatal error 'mutex is on list' at line 424 in file > /freebsd/svn_src/head/lib/libthr/thread/thr_mutex.c (errno = 2) > Abort (core dumped) This message typically mean that non-async signal safe function was called after fork in the multithreaded process.
Cannot say anything more useful. The backtrace below clearly indicates that a new thread was in the process of being created, but what was the global state of process ? > > Backtrace looks like: > > #0 0x000000080457648a in thr_kill () from /lib/libc.so.7 > #1 0x00000008045763f8 in raise () from /lib/libc.so.7 > #2 0x0000000804574959 in abort () from /lib/libc.so.7 > #3 0x000000080422660a in pthread_attr_getaffinity_np () from /lib/libthr.so.3 > #4 0x0000000804221c00 in pthread_mutex_destroy () from /lib/libthr.so.3 > #5 0x0000000810ee0aa9 in Array::decRef () from > /usr/local/lib/libpoppler.so.46 > #6 0x0000000810f524ef in Object::free () from /usr/local/lib/libpoppler.so.46 > #7 0x0000000810f07408 in Gfx::go () from /usr/local/lib/libpoppler.so.46 > #8 0x0000000810f06ecb in Gfx::display () from /usr/local/lib/libpoppler.so.46 > #9 0x0000000810f57058 in Page::displaySlice () > from /usr/local/lib/libpoppler.so.46 > #10 0x0000000810a3b3e2 in _poppler_page_render () > from /usr/local/lib/libpoppler-glib.so.8 > #11 0x000000081080df51 in register_evince_backend () > from /usr/local/lib/evince/4/backends/libpdfdocument.so > #12 0x000000081080d2c5 in register_evince_backend () > from /usr/local/lib/evince/4/backends/libpdfdocument.so > #13 0x0000000800ae4cc1 in ev_job_print_set_cairo () > from /usr/local/lib/libevview3.so.3 > #14 0x0000000800ae5bc0 in ev_job_scheduler_get_running_thread_job () > from /usr/local/lib/libevview3.so.3 > #15 0x00000008039360fa in g_thread_proxy () > from /usr/local/lib/libglib-2.0.so.0 > #16 0x000000080421b6e4 in pthread_create () from /lib/libthr.so.3 > #17 0x0000000000000000 in ?? () > > I'm not sure if these two observations are connected, but it was enough > to make -current unworkable for me... > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > p...@freebsd.org | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > _______________________________________________ > email@example.com mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"