* previously reported test case does not work in Cygwin 1.7.18
@ 2013-04-25 15:11 Andreas Steenpaß
2013-08-30 14:40 ` Andreas Steenpaß
0 siblings, 1 reply; 4+ messages in thread
From: Andreas Steenpaß @ 2013-04-25 15:11 UTC (permalink / raw)
To: cygwin
I have tried to run the following test case with the newest release:
http://cygwin.com/ml/cygwin/2012-12/msg00076.html
It used to work after it was fixed, but now it seems to be broken again.
Actually, it is even worse than before because now, not even thread 1
catches SIGUSR2:
$ uname -a
CYGWIN_NT-6.1-WOW64 zoppo 1.7.18(0.263/5/3) 2013-04-19 10:39 i686 Cygwin
$ ./testcase1
pid: 3628
thread 1 waiting for SIGUSR1
// from another console, send SIGUSR2, then SIGUSR1 (in this order!)
$ kill -SIGUSR2 3628
$ kill -SIGUSR1 3628
// The program catches only SIGUSR1, but not SIGUSR2:
thread 1 received SIGUSR1
thread 1 waiting for SIGUSR2
Best regards,
Andreas
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: previously reported test case does not work in Cygwin 1.7.18
2013-04-25 15:11 previously reported test case does not work in Cygwin 1.7.18 Andreas Steenpaß
@ 2013-08-30 14:40 ` Andreas Steenpaß
2013-08-30 21:32 ` Christopher Faylor
0 siblings, 1 reply; 4+ messages in thread
From: Andreas Steenpaß @ 2013-08-30 14:40 UTC (permalink / raw)
To: cygwin
I would like to bring the issue described below up again. I have just
tested this with Cygwin 1.7.24, and it shows the same behaviour as
before, so it seems that this bug still persists.
My system is:
$ uname -a
CYGWIN_NT-6.1-WOW64 zoppo 1.7.24(0.269/5/3) 2013-08-15 11:55 i686 Cygwin
Best regards,
Andreas
Le 25/04/2013 12:06, Andreas Steenpaà a écrit :
> I have tried to run the following test case with the newest release:
>
> http://cygwin.com/ml/cygwin/2012-12/msg00076.html
>
> It used to work after it was fixed, but now it seems to be broken again.
> Actually, it is even worse than before because now, not even thread 1
> catches SIGUSR2:
>
> $ uname -a
> CYGWIN_NT-6.1-WOW64 zoppo 1.7.18(0.263/5/3) 2013-04-19 10:39 i686 Cygwin
> $ ./testcase1
> pid: 3628
> thread 1 waiting for SIGUSR1
>
> // from another console, send SIGUSR2, then SIGUSR1 (in this order!)
> $ kill -SIGUSR2 3628
> $ kill -SIGUSR1 3628
>
> // The program catches only SIGUSR1, but not SIGUSR2:
> thread 1 received SIGUSR1
> thread 1 waiting for SIGUSR2
>
> Best regards,
> Andreas
>
>
> --
> 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
>
>
>
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: previously reported test case does not work in Cygwin 1.7.18
2013-08-30 14:40 ` Andreas Steenpaß
@ 2013-08-30 21:32 ` Christopher Faylor
2013-09-05 20:18 ` Andreas Steenpaß
0 siblings, 1 reply; 4+ messages in thread
From: Christopher Faylor @ 2013-08-30 21:32 UTC (permalink / raw)
To: cygwin
On Fri, Aug 30, 2013 at 04:40:44PM +0200, Andreas Steenpa? wrote:
>I would like to bring the issue described below up again. I have just
>tested this with Cygwin 1.7.24, and it shows the same behaviour as
>before, so it seems that this bug still persists.
>
>My system is:
>$ uname -a
>CYGWIN_NT-6.1-WOW64 zoppo 1.7.24(0.269/5/3) 2013-08-15 11:55 i686 Cygwin
This should be fixed in the most recent snapshot.
cgf
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: previously reported test case does not work in Cygwin 1.7.18
2013-08-30 21:32 ` Christopher Faylor
@ 2013-09-05 20:18 ` Andreas Steenpaß
0 siblings, 0 replies; 4+ messages in thread
From: Andreas Steenpaß @ 2013-09-05 20:18 UTC (permalink / raw)
To: cygwin
Le 30/08/2013 23:32, Christopher Faylor a écrit :
> On Fri, Aug 30, 2013 at 04:40:44PM +0200, Andreas Steenpa? wrote:
>> I would like to bring the issue described below up again. I have just
>> tested this with Cygwin 1.7.24, and it shows the same behaviour as
>> before, so it seems that this bug still persists.
>>
>> My system is:
>> $ uname -a
>> CYGWIN_NT-6.1-WOW64 zoppo 1.7.24(0.269/5/3) 2013-08-15 11:55 i686 Cygwin
> This should be fixed in the most recent snapshot.
I confirm that this works in Cygwin 1.7.25. Thank you for fixing this.
Best regards,
Andreas
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-09-05 20:18 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-04-25 15:11 previously reported test case does not work in Cygwin 1.7.18 Andreas Steenpaß
2013-08-30 14:40 ` Andreas Steenpaß
2013-08-30 21:32 ` Christopher Faylor
2013-09-05 20:18 ` Andreas Steenpaß
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).