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 Date: Tue, 20 Apr 2004 18:29:37 -0500 From: Brian Ford Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: cygwin1.dll problem with Hyperthreaded machines. In-Reply-To: Message-ID: References: <20040416214550 DOT GG26558 AT cygbert DOT vinschen DOT de> <20040416231802 DOT GA5050 AT coe DOT bosbc DOT com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-360817163-1082503777=:2464" X-IsSubscribed: yes ---559023410-360817163-1082503777=:2464 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 16 Apr 2004, Brian Ford wrote: > On Fri, 16 Apr 2004, Christopher Faylor wrote: > > > On Fri, Apr 16, 2004 at 11:45:50PM +0200, Corinna Vinschen wrote: > > >On Apr 16 17:03, Chuck McDevitt wrote: > > >>Has anyone had a chance to try reproducing my problem with Cygwin1.dll > > >>and Hyperthreaded machines? > > > > > >I, for one, have no hyperthreading machine available. > > > > I have one available but it's not running Windows and I have no spare > > disk space on which to add Windows (my hyperthreaded system is a > > laptop). I've actually run out of space for desktop computers now. > > > > Maybe Corinna has more space than I do. :-) > > > > Getting a hyperthreading machine in the hands of a developer is probably > > the only way this will be solved. And, I don't mean remote login or > > having someone else do remote debugging. > > I have one :-), and this type of problem is import to me/us. But, I won't > be able to look at it until at least Monday. (It's a work machine, my > home machine is pitiful). This is just in case it rings a bell with another developer. I haven't had time to investigate yet as I just reproduced it. I'll try to dig deeper as time allows. Attached is the script I used to reproduce it. Just run it while doing other usefull work and wait for it to stop sucking CPU as shown in the task manager. It may show up on non-hyperthreaded machines. $ uname -a CYGWIN_NT-5.1 fordpc 1.5.10(0.114/4/2) 2004-04-20 14:21 i686 unknown unknown Cygwin One time I saw: C:\cygwin\bin\bash.exe (3264): *** name not NULL? id 0x444, i 2 Here is the stack dump: (gdb) thread 1 [Switching to thread 1 (thread 1504.0xbf8)]#0 0x7ffe0304 in ?? () (gdb) bt #0 0x7ffe0304 in ?? () #1 0x77f5b5d4 in ntdll!ZwClose () from /cygdrive/c/WINDOWS/System32/ntdll.dll #2 0x77e7a730 in KERNEL32!CloseHandle () from /cygdrive/c/WINDOWS/system32/kernel32.dll #3 0x00000670 in ?? () #4 0x6100811d in close_handle ( func=0x61077ff0 "virtual int fhandler_pipe::close()", ln=103, h=0x670, name=0x61078013 "get_handle ()", force=0) at ../../../../cygwin/winsup/cygwin/debug.cc:227 #5 0x610780cb in fhandler_pipe::close (this=0x616e50a4) at ../../../../cygwin/winsup/cygwin/pipe.cc:103 #6 0x610a05d4 in close (fd=3) at ../../../../cygwin/winsup/cygwin/cygheap.h:303 #7 0x61092bcf in _sigfe () at ../../../../cygwin/winsup/cygwin/cygserver.h:82 [snip junk and vauge stuff about fhandler_pipe::get_guard ()] #37 0x610280be in set_signal_mask (newmask=16, oldmask=1628039794) at ../../../../cygwin/winsup/cygwin/exceptions.cc:938 #38 0x00000000 in ?? () from (gdb) thread 2 [Switching to thread 2 (thread 1504.0x1f8)]#0 0x7ffe0304 in ?? () (gdb) bt #0 0x7ffe0304 in ?? () #1 0x77f5bfb4 in ntdll!ZwReadFile () from /cygdrive/c/WINDOWS/System32/ntdll.dll #2 0x77e7abbd in ReadFile () from /cygdrive/c/WINDOWS/system32/kernel32.dll [snip junk] #20 0x6109743c in sig_clear (target_sig=0) at ../../../../cygwin/winsup/cygwin/sigproc.cc:559 ---Type to continue, or q to quit--- #21 0x61099156 in wait_sig (self=0x610fd798) at ../../../../cygwin/winsup/cygwin/sigproc.cc:1111 #22 0x61003466 in cygthread::stub (arg=0x610fd798) at ../../../../cygwin/winsup/cygwin/cygthread.cc:65 #23 0x61004394 in _cygtls::call2 (func=0, arg=0x704, buf=0xbbf0dc) at ../../../../cygwin/winsup/cygwin/cygtls.cc:93 #24 0x6100434a in _cygtls::call (func=0, arg=0x0) at ../../../../cygwin/winsup/cygwin/cygtls.cc:82 HTH. If not, I'll keep digging :-). Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 ---559023410-360817163-1082503777=:2464 Content-Type: APPLICATION/x-sh; name="hthang.sh" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="hthang.sh" IyEgL2Jpbi9iYXNoCndoaWxlIDo7IGRvCiAgbXlwd2Q9YHB3ZGAKICBpZiB0 ZXN0IC16ICIkbXlwd2QiOyB0aGVuCiAgICBlY2hvICJUZXN0IGZhaWxlZCwg bXlwd2QgaXMgZW1wdHkuIiAKICAgIGV4aXQgMQogIGZpCmRvbmUK ---559023410-360817163-1082503777=:2464 Content-Type: text/plain; charset=us-ascii -- 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/ ---559023410-360817163-1082503777=:2464--