Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Subject: Re: FW: wish84 incredibly slow From: fergus Reply-To: fergus AT bonhard DOT uklinux DOT net To: cygwin AT cygwin DOT com In-Reply-To: References: <200406130626 DOT i5D6QrgN013801 AT mailgw01 DOT flightsafety DOT com> Content-Type: text/plain Message-Id: <1087243023.2859.2.camel@x1-6-00-0b-db-b9-16-dc> Mime-Version: 1.0 Date: Mon, 14 Jun 2004 20:57:03 +0100 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 14 Jun 2004 19:57:08.0424 (UTC) FILETIME=[C62E7480:01C45249] On Mon, 2004-06-14 at 19:56, Brian Ford wrote: > Um..., nevermind. That would probably not be useful. All that time elapses between these two calls: > > 876 6251810 [main] wish84 3360 path_conv::check:this->path(g:\home\user\wishrc.tcl), has_acls(0) > 35680785 41932595 [unknown (0xA64)] wish84 3360 _cygtls::remove: wait 0xFFFFFFFF > > and since the debug print for the unknown thread is at the beginning of the _cygtls::remove function, that is not the problem. Thank you for looking. Fergus -- 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/