From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 24 20:56:59 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C202EC2B for ; Tue, 24 Jun 2014 20:56:59 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3429A2D48 for ; Tue, 24 Jun 2014 20:56:59 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id s5OKsKd2061261; Tue, 24 Jun 2014 23:54:20 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua s5OKsKd2061261 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.8/Submit) id s5OKsKjk061260; Tue, 24 Jun 2014 23:54:20 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 24 Jun 2014 23:54:20 +0300 From: Konstantin Belousov To: Grzegorz Blach Subject: Re: Crash probably in libthr Message-ID: <20140624205420.GZ93733@kib.kiev.ua> References: <53A95016.3090901@blach.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zOTFI1MayFoZtDo5" Content-Disposition: inline In-Reply-To: <53A95016.3090901@blach.pl> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 20:56:59 -0000 --zOTFI1MayFoZtDo5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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-d= imurhxlz4tvytoxnfup/valgrind2.log > Backtrace from gdb: > https://phab.enlightenment.org/file/data/zvbelqzjt4h3ppates6a/PHID-FILE-d= snaw3golsozpzlb7uqe/gdb2.log >=20 > 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. --zOTFI1MayFoZtDo5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJTqeV8AAoJEJDCuSvBvK1BaQkP/3lenWjs4wFntulSJ41FMECV DO/mCd95159kNwj7BleGL6k4X3SNSQmQBCBHUahhW74f+305RM2NP+6b7ZN9j6OA 4oApYARDjpDivaJ/NR9XkqqOb1vjbGrwIdY+DYnaewAcpxL1+CpAULPFNdlw6FkR vjMzZK59hcti1ijH452P87romRWfv0U4hO05nzqp9d1KBE3UVrMz7CdGgSx/+of+ OKX9IksW1ip4woUCiXjQSi/J8AqJglD4ukPIaSoyUYW7CFHxWhWSleIWJzljUbFw oEx85+2HlIzRPfNzrdvqAfa4JZU4dNfIC1DAeNj7t3TX4pE/Fu4JT9Eb7JC4O7Tr 1iSfTI5hutFmoL61uF9L2/aDn49FCWhwh2Fr6yN9+FMSpE/8XxFIanJFzaJ48TZ3 aF3UyYW0o13zZdmAvyfmxxBvrjlsApLj+ghGhDirWXuwuJmqZpxD9FpLygT0cum6 D1J2FCWdbsNJeFLS/oj4LsoHm8QefaWqj9ega7Uj3mOR7qotf7pRFTwEaYynAgs0 8Re6XNr3O47cfqzOQI3pPWWt910Up0wtJIHpQ8pjybSRvEJkIKv55VsvlRfuWhej 323svhgl3T7NAUfsKneYRbo8R9AGE8ADL5nqKNcMegIF9CxVrwzX4xzhcftrWJ8Q 0r4EFFzRVdy3xNnJ+o// =CwyO -----END PGP SIGNATURE----- --zOTFI1MayFoZtDo5--