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
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
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
The test case works with the newest snapshot (20130401). Thanks for the fix!
Best regards,
Andreas
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:
Le 05/04/2013 19:41, Christopher Faylor a écrit :
On Fri, Apr 05, 2013 at 07:30:42PM +0200, Andreas Steenpa? wrote:
The test case works with the newest snapshot (20130401). Thanks for the fix!
Thanks for the feedback.
I haven't advertised a fix yet because there is still something not quite
Le 05/04/2013 21:32, Christopher Faylor a écrit :
On Fri, Apr 05, 2013 at 09:25:16PM +0200, Andreas Steenpa? wrote:
Le 05/04/2013 19:41, Christopher Faylor a ?crit :
On Fri, Apr 05, 2013 at 07:30:42PM +0200, Andreas Steenpa? wrote:
The test case works with the newest snapshot (20130401).
Le 30/03/2013 04:16, Andrey Repin a écrit :
Knowing, which VM it is, and what is the container settings in regard to
hardware virtualisation support, would be helpful.
The admin of this system wrote:
VMware 4.1.0 (ESXi 4.1)
Host configuration: standard configuration for Windows, 64bit
CPU: 1
Le 29/03/2013 14:29, Christopher Faylor a écrit :
On Thu, Mar 28, 2013 at 02:30:53PM +0100, Andreas Steenpa? wrote:
I have noticed that sometimes SIGCHLD is not delivered when a child
process exits. I can reproduce this behaviour reliably under the
following, very special circumstances:
I've
I have noticed that sometimes SIGCHLD is not delivered when a child
process exits. I can reproduce this behaviour reliably under the
following, very special circumstances:
* Immediately before calling 'exit(0);', the child process calls some
command 'system(...);'.
* SIGCHLD is blocked.
* A
Le 07/12/2012 18:38, Christopher Faylor a écrit :
This should be fixed in CVS and in the upcoming snapshot.
Thank you.I tested the snapshot, and this works now.
I have three more things (please tell me if I should start new threads
for these):
1) When will the next official version of Cygwin
Le 07/12/2012 02:27, Christopher Faylor a écrit :
I don't see any difference between Cygwin and Linux when I run the
test program.
cgf
I re-compiled and ran the test program under Cygwin 1.7.17 as well as on
several Linux machines (Debian/Fedora/Gentoo/Ubuntu, kernel versions
I have noticed that sigwait() does not return immediately if called in
the following situation:
* One of the signals the command is looking for isalready pending.
* This signal was send to the entire process rather than to a specific
thread.
* sigwait() is called from a thread other than the
12 matches
Mail list logo
