Hi,
I think that this is a problem in cygthreads, but since I have been
looking at cygwin for less than two weeks I might as well be quite
mistaken.
The problem can be reproduced with Cygwin 1.7.9-1 and also with
today's checkout of the code.
To repro run this program form the attachment (compil
On Thu, Aug 25, 2011 at 08:06:08PM +0100, Rafal Zwierz wrote:
>* cygthread.cc (cygthread::simplestub): Notify that the thread has
>detached also in freerange thread case.
Looks good. I'll check this in. Thanks.
cgf
Hi all,
Based on the feedback on cygwin-dev, I've put together a revised pair of
faq.using entries: one listing briefly the symptoms of fork failures and
what to do about it, and the other giving some details about why fork
fails (sometimes in spite of everything we do to compensate).
Hi all,
Based on the feedback from cygwin-dev, I've put together a revised pair
of faq.using entries: one listing briefly the symptoms of fork failures
and what to do about it, and the other giving some details about why
fork fails (sometimes in spite of everything we do to compensate).
Ooops. Mailer hiccup. Please ignore this one.
On 25/08/2011 10:08 PM, Ryan Johnson wrote:
Hi all,
Based on the feedback on cygwin-dev, I've put together a revised pair
of faq.using entries: one listing briefly the symptoms of fork
failures and what to do about it, and the other giving some de
