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 17:24:06 +0400 From: Egor Duda X-Mailer: The Bat! (v1.45) Personal Reply-To: Egor Duda Organization: DEO X-Priority: 3 (Normal) Message-ID: <161241708588.20000904172406@logos-m.ru> To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: testsuite signal handling patch In-reply-To: <006c01c0166a$1d308f40$0201a8c0@sos> References: <51226485839 DOT 20000904131022 AT logos-m DOT ru> <147231928395 DOT 20000904144106 AT logos-m DOT ru> <006c01c0166a$1d308f40$0201a8c0 AT sos> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Monday, 04 September, 2000 Sergey Okhapkin sos AT prospect DOT com DOT ru wrote: >> btw, shouldn't call_handler() set signal handler to SIG_DFL while >> program is in handler? SO> It depends of how the handler was set. It's true for signal() call, but the SO> behavior for sigaction() call should depend of sa_mask and sa_flags fields SO> of struct sigaction. i mean that cygwin doesn't seem to honor sa_flags currently. as far as i understood from sources, we should pass pointer to pinfo->sigs[signo] and sigsave.func as parameters to _sigreturn; and interrupt_now should set siga.handler to SIG_DFL, if sa_flags contains SA_RESETHAND Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19