public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Bug: Synchronous signals broken on Cygwin 64
Date: Thu, 26 Apr 2018 11:02:00 -0000	[thread overview]
Message-ID: <26e03635c83cba20a1ef68e238e41ec2@smtp-cloud9.xs4all.net> (raw)
In-Reply-To: <4a3b47db-fcdb-85f0-ec80-4cffcb7c495a@users.sourceforge.net>

On Thu, 26 Apr 2018 12:52:54, Thomas Zimmermann wrote:

> Hi
> 
> Am 26.04.2018 um 12:45 schrieb Houder:
> >> The expected behavior is that an installed signal handler runs exactly
> >> once for a signal and the OS terminates the program if the handler
> >> returns. This works on 32-bit Cygwin. From my observation, Cygwin 64
> >> differs in the follow ways:
> >=20
> > .. uhm, unless SA_RESETHAND (sa_flags) has been specified, I expect the
> > handler to be invoked again and again ...
> 
> What I mean is that the installed signal handler is re-called constantly
> for the same HW exception (div-by-zero in this case). It is as if
> there's an endless loop around the signal-handler function.

After the invocation of the handler, the program continues with the code
that attempts 'to divide by zero'.

As result of that, the handler is invoked again.

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

  reply	other threads:[~2018-04-26 11:02 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 [this message]
2018-04-26 11:09       ` Thomas Zimmermann
2018-04-26 11:13       ` Thomas Zimmermann
2018-04-26 12:58         ` Houder
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=26e03635c83cba20a1ef68e238e41ec2@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).