X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.0 required=5.0 tests=AWL,BAYES_50,SPF_PASS,WEIRD_PORT
X-Spam-Check-By:	sourceware.org
Message-ID:	<49A57E6B.7060508@gmail.com>
Date:	Wed, 25 Feb 2009 17:22:51 +0000
From:	Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent:	Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.5.25: pthread/ofstream problem
References:	<D24C564ACEAD16459EF2526E1D7D605D0C054FE83C AT IMCMBX3 DOT MITRE DOT ORG>
In-Reply-To:	<D24C564ACEAD16459EF2526E1D7D605D0C054FE83C@IMCMBX3.MITRE.ORG>
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

Filipek, Stefan R. wrote:

> Note that this problem seems to be accelerated by having the target
> directory open in explorer and/or having the files highlighted. I've come
> across situations where even ofstream.open() will throw an exception when
> doing the above. The exception has been seen in both C++ and python, which
> makes me think it's something fundamental in Cygwin, and possibly related
> to this as well.

  Actually, that makes me think you have BLODA-style interference.

> Potential app conflicts:
>
> ZoneAlarm Personal Firewall
> Detected: HKLM Registry Key, Named file.

  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?

  The stack trace you posted suggests BLODA too:

[ minor munging of paths to simplify
~ $ addr2line --exe /bin/cygwin1.dbg
610B5FF2
/usr/src/cygwin-1.5.25-15/winsup/cygwin/thread.cc:1593
610B8B0D
/usr/src/cygwin-1.5.25-15/winsup/cygwin/thread.h:147
610B1E4B
/usr/src/cygwin-1.5.25-15/winsup/cygwin/thread.h:301
610779F8
/usr/src/cygwin-1.5.25-15/winsup/cygwin/pthread.cc:71
610935A8
??:0
610060D8
/usr/src/cygwin-1.5.25-15/winsup/cygwin/dcrt0.cc:956
61004416
/usr/src/cygwin-1.5.25-15/winsup/cygwin/cygtls.cc:73

  Looking at the top of the stack there:

  1590  pthread_mutex::~pthread_mutex ()
  1591  {
  1592    if (win32_obj_id)
  1593      CloseHandle (win32_obj_id);
  1594
  1595    mutexes.remove (this);
  1596  }

suggests that a plain call to win32.CloseHandle blew up in our faces.  That
really does smack of a bad AV/PFW hook that's messing with handles.

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

  No, of course not; any failures are real bugs.  However, nobody's going to
be very likely to fix it in 1.5, so you should definitely see if it reproduces
under 1.7.  If you can't narrow it down to a BLODA, that is.

    cheers,
      DaveK



--
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/

- Raw text -