On Sunday, June 12, 2005 T 5:37 PM, Mark Pizzolato wrote:
On Friday, June 10, 2005 at 3:44 PM, Mark Pizzolato wrote:
> On Thursday, June 09, 2005 at 6:12 PM, Mark Pizzolato wrote:
>> On Thursday, June 09, 2005 at 3:35 PM, Christopher Faylor wrote:
>> > On Wed, Jun 08, 2005 at 05:43:59PM -0700, M
On Friday, June 10, 2005 at 3:44 PM, Mark Pizzolato wrote:
> On Thursday, June 09, 2005 at 6:12 PM, Mark Pizzolato wrote:
>> On Thursday, June 09, 2005 at 3:35 PM, Christopher Faylor wrote:
>> > On Wed, Jun 08, 2005 at 05:43:59PM -0700, Mark Pizzolato wrote:
>> > >There is a serious problem for m
On Thursday, June 09, 2005 at 6:12 PM, Mark Pizzolato wrote:
On Thursday, June 09, 2005 at 3:35 PM, Christopher Faylor wrote:
> On Wed, Jun 08, 2005 at 05:43:59PM -0700, Mark Pizzolato wrote:
> >There is a serious problem for multi threaded programs doing simple I/O
> >operations in cygwin (open,
On Thursday, June 09, 2005 at 3:35 PM, Christopher Faylor wrote:
On Wed, Jun 08, 2005 at 05:43:59PM -0700, Mark Pizzolato wrote:
>There is a serious problem for multi threaded programs doing simple I/O
>operations in cygwin (open, dup, fdopen, fclose, and close).
>
>The attached 81 line test prog
On Wed, Jun 08, 2005 at 05:43:59PM -0700, Mark Pizzolato wrote:
>There is a serious problem for multi threaded programs doing simple I/O
>operations in cygwin (open, dup, fdopen, fclose, and close).
>
>The attached 81 line test program clearly demonstrates the issue (by
>hanging and no longer con
There is a serious problem for multi threaded programs doing simple I/O
operations in cygwin (open, dup, fdopen, fclose, and close).
The attached 81 line test program clearly demonstrates the issue (by hanging
and no longer consuming CPU or performing any I/O operations).
I'm sure that anyone
6 matches
Mail list logo
