delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/02/09/15:49:26

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
To: cygwin AT cygwin DOT com
From: CV <or254498 AT hotmail DOT com>
Subject: 20050208 hyperthreading bug is back ?
Date: Wed, 9 Feb 2005 20:47:12 +0000 (UTC)
Lines: 52
Message-ID: <loom.20050209T210756-355@post.gmane.org>
Mime-Version: 1.0
X-Complaints-To: usenet AT sea DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: main.gmane.org
User-Agent: Loom/3.14 (http://gmane.org/)
X-Loom-IP: 82.158.81.106 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217)
X-Gmane-MailScanner: Found to be clean
X-Gmane-MailScanner: Found to be clean
X-MailScanner-From: goc-cygwin AT m DOT gmane DOT org
X-MailScanner-To: cygwin AT cygwin DOT com
X-IsSubscribed: yes

Summary:
--------
I reported before that the 20050206 snapshot appeared to fix
the hyperthreading bug for me.

Now it seems that the next snapshot 20050208 broke it again.

Test Case:
----------
Command:
  find z | while read f; do chown username "$f"; done;

and a longer version of the test case command, (same results):
  export i=1; find z | while read f; do printf "%8i: %s\n" $i "$f"; \
  chown username "$f"; ((i++)); done;

Note: z is a directory tree under /cygdrive/c with 4000 odd files in it.

Result:
-------
  after 700 to 1000 files bash hangs with the following error message:
  2 [exiting thread] bash 3328 cygthread::stub: erroneous thread
    activation, name is NULL

The first number varies (2, 4, 8) as well as the number after "bash"
which I take it is the pid.

NOTE: The error only occurs when I run this from the command prompt.
I put the same command in a file (preceded by a #!/bin/bash -line)
and called it chownz.bash
./chownz.bash completes as expected
. ./chownz.bash also completes as expected

The same test runs without problems on the 20050206 snapshot.

My system:
----------
HP Pavilion, P4HT3.2G, 1G memory, 200G SCSI HD

$ uname -a
CYGWIN_NT-5.1 nodename 1.5.13s(0.118/4/2) 20050208 14:21:58 i686
  unknown unknown Cygwin

I tried to include the output from
  'cygcheck -s -v -r | tee cygcheck.out'
but the interface will not accept lines longer than 80 chars.
I can mail it across, just let me know.

Regards CV




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


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019