testsuite signal handling patch

Egor Duda deo@logos-m.ru
Mon Sep 4 10:42:00 GMT 2000


Monday, 04 September, 2000 Chris Faylor cgf@cygnus.com wrote:

CF> On Mon, Sep 04, 2000 at 02:41:06PM +0400, Egor Duda wrote:
>>Monday, 04 September, 2000 Egor Duda deo@logos-m.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:

       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@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19

More information about the Cygwin-developers mailing list