Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
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 21:41:11 +0400
From: Egor Duda <deo AT logos-m DOT ru>
X-Mailer: The Bat! (v1.45) Personal
Reply-To: Egor Duda <cygwin-developers AT sources DOT redhat DOT com>
Organization: DEO
X-Priority: 3 (Normal)
Message-ID: <115257133328.20000904214111@logos-m.ru>
To: Chris Faylor <cygwin-developers AT sources DOT redhat DOT com>
Subject: Re: testsuite signal handling patch
In-reply-To: <20000904131036.A24177@cygnus.com>
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-Transfer-Encoding: 7bit

Hi!

Monday, 04 September, 2000 Chris Faylor cgf AT cygnus DOT com wrote:

CF> On Mon, Sep 04, 2000 at 02:41:06PM +0400, Egor Duda wrote:
>>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?

CF> No.

to  be  more  precise,  "...  if handler was set with signal() call or
sigaction call with appropriate flag?"

linux man page for sigaction contains the followin text:

===============================================================
...
SA_ONESHOT or SA_RESETHAND
       Restore  the  signal  action  to the default
       state  once  the  signal  handler  has  been
       called.   (This  is  the default behavior of
       the signal(2) system call.)
===============================================================

glibc   doc,   otoh,   says   that  signal  which is currently handled
should     be  blocked.  susv2  says nothing specific. maybe someone
quote what posix or ansi say about this?

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19