From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Bug: Synchronous signals broken on Cygwin 64
Date: Thu, 26 Apr 2018 12:58:00 -0000 [thread overview]
Message-ID: <4c43d9608bc106299632d6063ed02891@smtp-cloud9.xs4all.net> (raw)
In-Reply-To: <46f53185-1295-e1b8-0121-103f2b7c4f1f@users.sourceforge.net>
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
next prev parent reply other threads:[~2018-04-26 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 7:58 Thomas Zimmermann
2018-04-26 10:44 ` Marco Atzeri
2018-04-26 10:45 ` Houder
2018-04-26 10:53 ` Thomas Zimmermann
2018-04-26 11:02 ` Houder
2018-04-26 11:09 ` Thomas Zimmermann
2018-04-26 11:13 ` Thomas Zimmermann
2018-04-26 12:58 ` Houder [this message]
2018-04-26 10:55 ` Houder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4c43d9608bc106299632d6063ed02891@smtp-cloud9.xs4all.net \
--to=houder@xs4all.nl \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).