From mint-bounce@lists.fishpool.fi Sun Jul 11 14:50:15 2010 Message-ID: <4C3A1213.40600@freesbee.fr> Date: Sun, 11 Jul 2010 20:48:51 +0200 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] read() and signals References: <4C389D1D.7030108@freesbee.fr> <1278789068.7311.1378.camel@jetpack.demon.co.uk> <4C39FD60.7040409@freesbee.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o6BIoF7V031929 Andreas Schwab wrote: >> Basically, the read() function should fail with EINTR when a signal is >> caught, but in MiNT it continues blocking. > > That's traditional BSD behaviour. Does it help to add SA_INTERRUPT to > sa_flags? It is not defined in the MiNTLib :-( -- Vincent Rivière