Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-ID: <19990708211407.21116.rocketmail@send205.yahoomail.com> Date: Thu, 8 Jul 1999 14:14:07 -0700 (PDT) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: Re: 19990705 snapshot To: cygwin developers MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Earnie Boyd wrote: > Hmm. Is it possible that the snapshots have become binary incompatible? > What > happens when Chris and DJ start an interactive session of bash within bash? > I > get a continual sequence of three errors from __get_signal_mutex followed by > one error from __block_sig_dispatch. > > Also, I can't use the WinNT task manager to kill this child task, as well C-c > and C-break don't do anything either. However, I can use the WinNt task > manager to kill the parent process. I can close the console window though. > > An interactive ash process always give one error of > hinfo::fixup_after_fork: unable to contact parent process but executes the > command. Ok, A little more on this. The .bashrc file contains export PS1='(`uname -r | cut -f 1 -d " "`)\@ \w> ' and if I comment this string it no longer loops or gives an error on startup. Also, the looping occurs if you are a ordinary domain user. If you are logged in locally as Adminstrator then you get one set of errors, no looping. Commenting out the export PS1 string stopped the error messages from bash but if I start an interactive session of bash in bash and execute an external command I get the error "hinfo::fixup_after_fork: unable to contact parent process" and the process freezes. At this point hitting C-c causes the following errors: 0 0 [main] c:\root\snap\bin\bash.exe 1003 hinfo::fixup_after_fork: una ble to contact parent process 0 0 [sig] c:\root\snap\bin\bash.exe 1002 call_handler: couldn't get co ntext of main thread, Win32 error 5 ****** ../../../devo/winsup/sigproc.cc:225 __get_signal_mutex failed, res 258, W in32 error 0 0) function ../../../devo/winsup/exceptions.cc, line 468 ****** ../../../devo/winsup/debug.cc:135 __get_signal_mutex failed, res 258, Win 32 error 6 0) function ../../../devo/winsup/exceptions.cc, line 468 ****** ../../../devo/winsup/debug.cc:135 __get_signal_mutex failed, res 258, Win 32 error 288 0 10043686 [main] bash 1002 __block_sig_dispatch: WFSO(signal_mutex<0x20>) f ailed, Win32 error 6 At this point the only action left is to close the console window. I tried doing the strace after starting the second occurance of bash for the executed command but no file was created. I'll keep trying to get some strace to show the errors, so far I've been unsuccessful at doing so. Another question: has the CYGWIN=strace=1,somefile functionality been deprecated with the advent of the strace program? === Earnie Boyd Newbies, please visit (If you respond to the list, then please don't cc me) _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com