From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29028 invoked by alias); 26 Apr 2018 12:58:46 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 29017 invoked by uid 89); 26 Apr 2018 12:58:45 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=Best X-HELO: lb3-smtp-cloud9.xs4all.net Received: from lb3-smtp-cloud9.xs4all.net (HELO lb3-smtp-cloud9.xs4all.net) (194.109.24.30) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 26 Apr 2018 12:58:40 +0000 Received: from tmp.oQffEZSHW1 ([83.162.234.136]) by smtp-cloud9.xs4all.net with ESMTPSA id BgTsfypH2bfBnBgTufSOGL; Thu, 26 Apr 2018 14:58:38 +0200 Date: Thu, 26 Apr 2018 12:58:00 -0000 Message-ID: <4c43d9608bc106299632d6063ed02891@smtp-cloud9.xs4all.net> From: Houder Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: Bug: Synchronous signals broken on Cygwin 64 References: <4a3b47db-fcdb-85f0-ec80-4cffcb7c495a@users.sourceforge.net> <26e03635c83cba20a1ef68e238e41ec2@smtp-cloud9.xs4all.net> <46f53185-1295-e1b8-0121-103f2b7c4f1f@users.sourceforge.net> In-Reply-to: <46f53185-1295-e1b8-0121-103f2b7c4f1f@users.sourceforge.net> Content-Type: text/plain; charset=UTF-8; format=fixed User-Agent: mua.awk 0.99 X-CMAE-Envelope: MS4wfG4gTuPhFcLpd+zp/MGY4ZuwX9z9jop/1DqhlQFo4fj1vweVYgcDBsGgMIORTwDA+AcyKQTognJ6bmBaG/tirvQTZzq8dULPPGeZ/GXH9Inrtz18O64m GQjXhiT/H4REe7frIcM6oAEAWLswqUntLeyDca1P6zy1cI+17b4vRYbe6YdWCo8XMf1xII55/4ba4A== X-SW-Source: 2018-04/txt/msg00324.txt.bz2 On Thu, 26 Apr 2018 13:12:53, Thomas Zimmermann wrote: > > > After the invocation of the handler, the program continues with the code > > > that attempts 'to divide by zero'. > > >=20 > > > As result of that, the handler is invoked again. > > > > This means that the behavior of the test case is incorrect when running > > in 32-bit mode. There, the signal-handler function runs exactly *once* > > and then the program terminates. > > > I just saw that the result after returning from a synchronous signal is > undefined. So any behavior seems be OK. I'd still encourage to unify the > behavior of 32-bit and 64-bit code. (See my other mail.) You are correct. For those who like a textbook reference, see: Chapter 22, section 4 (Hardware-Generated Signals) of The Linux Programming Interface by Michael Kerrisk. Henri > Best regards > Thomas -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple