This is the mail archive of the
mailing list for the Cygwin project.
Re: All clear (was Re: 2012-03-19 snapshot problematic (was Re: cygwin-1.7.10-1 fork - address space needed by ... already in use))
On Thu, Mar 22, 2012 at 03:37:32PM +0100, Denis Excoffier wrote:
>On Thu, Mar 22, 2012 at 09:29:38AM -0400, Christopher Faylor wrote:
>>> On Thu, Mar 22, 2012@07:56:32AM +0100, Denis Excoffier wrote:
>>> >- in tcsh: several concurrent combinations of 'make -j 3', 'make',
>>> > fg, Control-Z, bg, which has shown to make tcsh to expose '(badjob)'
>>> > and the PC to hang sometimes.
>>> Are you saying that there *is* a problem with the current snapshot? Or
>>> that you saw a problem with this in 1.7.11 or that you have always seen
>>> a problem with this?
>I'm saying that i'll try this sort of thing, since this failed
>with the snapshot 20120314. I tried this morning, and definitely yes,
>the '(badjob)' is rather easy to obtain, but now i know that this is
>a (well known) tcsh problem (see BUGS in the tcsh distribution), and
>has nothing to do with cygwin1.dll. When you finally kill the process
>that tcsh has lost, everything returns in order.
>I also compiled GCC 4.7.0 successfully with no message.
>In any case, with this snapshot 20120321 16h UTC, i was not able to
>make the PC hang (i tried it). In my opinion this is the best 1.7 we
>have ever had.
Thanks for confirming and thanks for keeping the reports coming.
I don't think I mentioned that *I think* that my recent changes should
have made cygwin a little faster since I removed some synchronization
points which might have caused occasional stalls in process creation.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple