I want to go on record that it happening to us, too. And, I can say
that it is happening *much* more since I moved to this machine:
2x AMD Opteron 6134 (16 cores total)
Server 2008 R2 Enterprise, Service Pack 1
Software we have installed on the machine:
ActivePerl
AVG 9.0
Chrome
Jav
On Apr 29 11:35, John Dong wrote:
> Hi,
>
> Cygwin on Windows 7, seems to exhibit a rather peculiar behavior: Sometimes
> the exit status of a Win32 process is incorrectly captured by Cygwin.
Please:
http://cygwin.com/acronyms/#PCYMTWLL
http://cygwin.com/acronyms/#TOFU
> [...]
> > int _tmain(
On Wed, May 25, 2011 at 07:20:35PM -0700, John Dong wrote:
>It's nice to hear from Edward that we're not the only ones to notice
>this behavior.
>
>Of course, patches would be nice, and I would be interested in digging
>in into this if someone familiar with Cygwin's codebase would be
>willing to en
Hi Chris,
It's nice to hear from Edward that we're not the only ones to notice this
behavior.
Of course, patches would be nice, and I would be interested in digging in into
this if someone familiar with Cygwin's codebase would be willing to enlighten
me as to the codepath for grabbing Win32 p
On Wed, May 25, 2011 at 10:16:03AM -0400, Edward Lam wrote:
>On 29/04/2011 2:35 PM, John Dong wrote:
>> Reproducing this seems nondeterministic -- sometimes I can get it to
>> happen in 5 minutes, other times it takes overnight. I've tried using
>> a different shell (like dash), but it doesn't make
On 29/04/2011 2:35 PM, John Dong wrote:
Reproducing this seems nondeterministic -- sometimes I can get it to
happen in 5 minutes, other times it takes overnight. I've tried using
a different shell (like dash), but it doesn't make a difference,
leading me to suspect this to be a lower-level issue
I can still reproduce this on the latest snapshot. I also tried some different
hardware and virtual machines too, and I don't think my machine is to blame.
Has anyone else been able to reproduce this bug? Or have pointers of further
things I can do to diagnose it?
Thanks in advance,
John
On
Hi Edward,
For what it's worth, I just left it running since my last reply and it's still
running. I can fairly confidently say this only happens when executing a
Windows binary from Cygwin.
Any insights or suggestions of further things to test would be greatly
appreciated. These kinds of bugs
Hi Edward,
Yeah, I forgot to mention that I tried scripting it in a batch file outside
cygwin in much the same way as your script, and it ran for a day or two without
fail. I can keep that going for longer just in case it fails less frequently,
but I don't think it's a Windows / MSVCRT bug.
J
On Fri, Apr 29, 2011 at 13:35, John Dong wrote:
>I've tried using a different shell (like dash), but it doesn't make a
>difference, leading me to suspect this to be a lower-level issue within the
>Cygwin DLL.
Have you tried it with the stock Windows command processor? Something
like this (untest
Hi,
Cygwin on Windows 7, seems to exhibit a rather peculiar behavior: Sometimes the
exit status of a Win32 process is incorrectly captured by Cygwin.
I'm running Cygwin 1.7.9(0.237/5/3) on Windows 7 64-bit, but I've reproduced
this behavior with every release of Cygwin 1.7 on both 32-bit and 64
11 matches
Mail list logo