From owner-freebsd-hackers@freebsd.org Sat Jan 23 21:52:41 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8FEDAA8F92F for ; Sat, 23 Jan 2016 21:52:41 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F2991F15 for ; Sat, 23 Jan 2016 21:52:41 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1aN66h-000GIr-Nm; Sun, 24 Jan 2016 00:52:31 +0300 Date: Sun, 24 Jan 2016 00:52:31 +0300 From: Slawa Olhovchenkov To: Ivan Radovanovic Cc: freebsd-hackers@FreeBSD.org Subject: Re: Unexpected (at least to me) kevent behavior on window size change when in X Message-ID: <20160123215231.GO88527@zxy.spb.ru> References: <56A3EDEE.1030400@gmail.com> <56A3F404.7020800@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56A3F404.7020800@gmail.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jan 2016 21:52:41 -0000 On Sat, Jan 23, 2016 at 10:43:32PM +0100, Ivan Radovanovic wrote: > On 01/23/2016 22:17, Ivan Radovanovic wrote: > > > > The only thing which is out of ordinary is that I am doing this from > > mono, but still I am directly invoking libc functions from it, so I > > don't think it can have anything with it. > > > > Definitely it is something mono specific (I would still love to hear if > somebody has idea what might cause it) - I just wrote little C program > to test for same thing and everything works as expected. May be this is mono mapping EINTR to 0?