Crash probably in libthr

[Konstantin Belousov]

On Tue, Jun 24, 2014 at 12:16:54PM +0200, Grzegorz Blach wrote:
> On https://phab.enlightenment.org/T1330 I reported a crash in
> Enlightenment. After analyzing backtraces from valgrind and gdb we think
> this might be a bug in libthr.
And how did you come to this conclusion ?

> Backtrace from valgrind:
> https://phab.enlightenment.org/file/data/wlcvu7kmb5blxmgtnk2p/PHID-FILE-dimurhxlz4tvytoxnfup/valgrind2.log
> Backtrace from gdb:
> https://phab.enlightenment.org/file/data/zvbelqzjt4h3ppates6a/PHID-FILE-dsnaw3golsozpzlb7uqe/gdb2.log
> 
> Have any one known what
> /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:37 does?

The gdb backtrace you posted reports that the SIGSEGV occured in the
thread with lwp id 100363.  According to the same log, innermost
frame for the thread is in _op_blend_p_dp_mmx(), which is line 11
in the file src/lib/evas/common/./evas_op_blend/op_blend_pixel_i386.c.

umtx_op is the syscall which typically parks thread in the kernel while
waiting for unblock.  It appeared in the log because your process is
multithreaded and that other thread slept waiting for an event.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20140624/e566e28e/attachment.sig>