[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] read() and signals

To: Vincent Rivière <vincent.riviere@freesbee.fr>
Subject: Re: [MiNT] read() and signals
From: Andreas Schwab <schwab@linux-m68k.org>
Date: Sun, 11 Jul 2010 20:44:40 +0200
Cc: mint@lists.fishpool.fi
In-reply-to: <4C39FD60.7040409@freesbee.fr> ("Vincent Rivière"'s message of "Sun, 11 Jul 2010 19:20:32 +0200")
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-id: <mint.lists.fishpool.fi>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
References: <4C389D1D.7030108@freesbee.fr> <1278789068.7311.1378.camel@jetpack.demon.co.uk> <4C39FD60.7040409@freesbee.fr>
Sender: mint-bounce@lists.fishpool.fi
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)

Vincent Rivière <vincent.riviere@freesbee.fr> writes:

> 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?

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Follow-Ups:
- Re: [MiNT] read() and signals
  - From: Vincent Rivière <vincent.riviere@freesbee.fr>

References:
- [MiNT] bash 4.1
  - From: Vincent Rivière <vincent.riviere@freesbee.fr>
- Re: [MiNT] bash 4.1
  - From: Alan Hourihane <alanh@fairlite.co.uk>
- [MiNT] read() and signals
  - From: Vincent Rivière <vincent.riviere@freesbee.fr>

Prev by Date: [MiNT] read() and signals
Next by Date: Re: [MiNT] read() and signals
Previous by thread: [MiNT] read() and signals
Next by thread: Re: [MiNT] read() and signals
Index(es):
- Date
- Thread