From mint-bounce@lists.fishpool.fi  Thu Feb 26 04:05:29 2009
Date: Thu, 26 Feb 2009 08:58:57 +0000 (GMT)
From: David Brownlee <abs@absd.org>
To: Alan Hourihane <alanh@fairlite.co.uk>
cc: mint <mint@fishpool.com>
Subject: Re: [MiNT] sigaction() and SA_RESTART / SA_INTERRUPT
In-Reply-To: <1235604184.13634.228.camel@jetpack.demon.co.uk>
Message-ID: <alpine.NEB.2.00.0902260857480.13606@localhost>
References: <alpine.NEB.2.00.0902252152510.13606@localhost> <1235604184.13634.228.camel@jetpack.demon.co.uk>
User-Agent: Alpine 2.00 (NEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; 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: abs@absd.org
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>

On Wed, 25 Feb 2009, Alan Hourihane wrote:

> On Wed, 2009-02-25 at 22:00 +0000, David Brownlee wrote:
>> 	Is there any way to SA_RESTART or SA_INTERRUPT in sa_flags
>>  	for sigaction() under mint? Ther are the two ways to
>>  	determine whether system calls should be restarted after
>>  	a signal?
>
> Nope, currently unsupported.

 	Ah bummer :(

 	Is there any docs on the signal implementation in MiNT? I notice
 	signal.h mentions that signal() defaults to BSD semantics, which
 	should include restartable system calls?

 	Thanks