From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Threads
Date: Fri, 24 Oct 2014 12:54:00 -0000 [thread overview]
Message-ID: <20141024125416.GK20607@calimero.vinschen.de> (raw)
In-Reply-To: <544A327E.9090006@dronecode.org.uk>
[-- Attachment #1: Type: text/plain, Size: 3179 bytes --]
On Oct 24 12:05, Jon TURNEY wrote:
> On 23/10/2014 16:37, Corinna Vinschen wrote:
> >On Oct 23 08:04, Ken Brown wrote:
> >>Yes, flags register corruption is exactly what Eli suggested in the other
> >>bug report I cited.
> >
> >The aforementioned patch was supposed to fix this problem and it is
> >definitely in the current 1.7.32 release...
>
> I didn't mean to suggest otherwise, just that perhaps a similar problem
> exists now.
>
> So I made the attached test case to explore that. Maybe I've made an
> obvious mistake with it, but on the face of it, it seems to demonstrate
> something...
>
> jon@tambora /
> $ gcc signal-stress.c -Wall -O0 -g
>
> jon@tambora /
> $ ./a
> failed: 2144210386 isn't equal to 2144210386, apparently
So it checks i and j for equality, fails, and then comes up with
"42 isn't equal to 42"? This is weird...
> Note there is some odd load dependency. For me, it works fine when it's the
> only thing running, but when I start up something CPU intensive, it often
> fails...
That's... interesting. I wonder if that only occurs in multi-core or
multi-CPU environments. The fact that i and j are not the same when
testing, but then are the same when printf is called looks like a
out-of-order execution problem.
Is it possible that we have to add CPU memory barriers to the sigdelayed
function to avoid stuff like this?
Corinna
> #include <assert.h>
> #include <sys/time.h>
> #include <signal.h>
> #include <stdio.h>
>
> long SmartScheduleInterval = 1; /* ms */
> long SmartScheduleTime = 0;
>
> static void
> SmartScheduleTimer(int sig)
> {
> if (sig != 0)
> SmartScheduleTime += SmartScheduleInterval;
> }
>
> void
> SmartScheduleStartTimer(void)
> {
> struct itimerval timer;
> timer.it_interval.tv_sec = 0;
> timer.it_interval.tv_usec = SmartScheduleInterval * 1000;
> timer.it_value.tv_sec = 0;
> timer.it_value.tv_usec = SmartScheduleInterval * 1000;
> setitimer(ITIMER_REAL, &timer, 0);
> }
>
> int main()
> {
> /* Set up the timer signal function */
> struct sigaction act;
> act.sa_handler = SmartScheduleTimer;
> sigemptyset(&act.sa_mask);
> sigaddset(&act.sa_mask, SIGALRM);
> if (sigaction(SIGALRM, &act, 0) < 0) {
> perror("sigaction failed");
> return -1;
> }
>
> /* start timer */
> SmartScheduleStartTimer();
>
> /* Loop forever, doing tests which should always succeed, with lots of signals */
> int x = 0;
> int i = 0;
> while (1) {
> x = i;
> int j = x;
> if (j != i)
> {
> printf("failed: %d isn't equal to %d, apparently\n", i, j);
> break;
> }
> i++;
> }
> return 0;
> }
> --
> 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
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-10-24 12:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 13:04 Threads Ken Brown
2014-10-20 16:43 ` Threads Corinna Vinschen
2014-10-20 19:03 ` Threads Corinna Vinschen
2014-10-20 19:58 ` Threads Ken Brown
2014-10-21 11:17 ` Threads Corinna Vinschen
2014-10-21 12:27 ` Threads Ken Brown
2014-10-23 11:31 ` Threads Jon TURNEY
2014-10-23 12:04 ` Threads Ken Brown
2014-10-23 15:37 ` Threads Corinna Vinschen
2014-10-23 18:07 ` Threads Achim Gratz
2014-10-23 20:32 ` Threads Ken Brown
2014-10-24 1:07 ` Threads Ken Brown
2014-10-24 9:46 ` Threads Corinna Vinschen
2014-10-24 11:05 ` Threads Jon TURNEY
2014-10-24 12:54 ` Corinna Vinschen [this message]
2014-10-24 13:52 ` Threads Corinna Vinschen
2014-10-26 11:58 ` Threads Ken Brown
2014-10-28 10:44 ` Threads Jon TURNEY
2014-10-28 11:40 ` Threads Corinna Vinschen
2014-10-28 13:47 ` Threads Ken Brown
2014-10-28 14:19 ` [GOLDSTARS] Threads Corinna Vinschen
2014-10-28 17:39 ` Andrew Schulman
2014-10-29 10:00 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2014-10-26 13:20 Threads Angelo Graziosi
2014-10-26 21:38 ` Threads Ken Brown
2014-10-27 10:21 ` Threads Corinna Vinschen
2000-02-04 6:32 Threads M Dipperstein
2000-02-04 8:06 ` Threads Mumit Khan
1997-03-19 10:28 Threads Davind Maharaj
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=20141024125416.GK20607@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).