X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.8 required=5.0 	tests=AWL,BAYES_50
X-Spam-Check-By: sourceware.org
From: "Filipek, Stefan R." <sfilipek AT mitre DOT org>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Date: Wed, 25 Feb 2009 15:05:06 -0500
Subject: Re: 1.5.25: pthread/ofstream problem
Message-ID: <D24C564ACEAD16459EF2526E1D7D605D0C054FEAB2@IMCMBX3.MITRE.ORG>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

>   Which version is this?  Is it the full version with antispyware and all
sorts of extra tricks built in?  What anti-virus do you have?

It's using Symantec Endpoint Protection 11.0.2000.1567 - all the bells and =
whistles.

I blamed AVS at first, but the problem also persists on machines that do no=
t have any AVS installed. I double checked and ran another test today on a =
different machine that also ended the same way (exact same spot too), but o=
nly at 100k iterations.

But, it should be noted that the stackdump has occurred at different points=
, in different threads (as opposed to main). I can try to provide those if =
anyone is interested.=20


>> Is there something inherently wrong with having different treads access
>> different files at once?=20

>  No, of course not; any failures are real bugs.

Thank you for the sanity check.


I'll test with 1.7 but I just wanted to say that it's not AVS/PFW to blame =
here. Could it possibly be Windows Explorer itself? Again, it does seem to =
occur more often when an explorer window is open to the output directory, i=
n which it refreshes the status of the files being opened/closed every so o=
ften.

It would also be nice to know if someone else can reproduce the issue; perh=
aps just leave it running on a computer overnight.

Regards,
Stefan

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/