Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Mon, 4 Sep 2000 13:43:32 -0400 From: Chris Faylor To: Egor Duda Subject: Re: testsuite signal handling patch Message-ID: <20000904134332.A24547@cygnus.com> Reply-To: cygwin-developers AT sources DOT redhat DOT com Mail-Followup-To: Egor Duda References: <51226485839 DOT 20000904131022 AT logos-m DOT ru> <147231928395 DOT 20000904144106 AT logos-m DOT ru> <20000904131036 DOT A24177 AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <20000904131036.A24177@cygnus.com>; from cgf@cygnus.com on Mon, Sep 04, 2000 at 01:10:36PM -0400 On Mon, Sep 04, 2000 at 01:10:36PM -0400, Chris Faylor wrote: >On Mon, Sep 04, 2000 at 02:41:06PM +0400, Egor Duda wrote: >>Hi! >> >>Monday, 04 September, 2000 Egor Duda deo AT logos-m DOT ru wrote: >> >>ED> currently, tests from winsup.api/ltp/ can possibly catch fatal >>ED> signals such as SIGSEGV recursively. attached patch fixes this. >> >>btw, shouldn't call_handler() set signal handler to SIG_DFL while >>program is in handler? > >No. Just to be a little more verbose, cygwin has AFAIK always followed the BSD behavior of keeping a signal armed. You're right that the sa_flags field isn't completely implemented. I keep waiting for someone to complain about that. It shouldn't be hard to do the right thing. I'll see what I can do. cgf