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 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: Facing problem with bash Date: Thu, 22 Jul 2004 22:40:16 +0530 Message-ID: <7837FAA857FF274AAE32F4AFA03272920124B2@mshyd2.hyd.deshaw.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Atukuri, Vasudeva_Kumar" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i6MHAVSj019749 OS: Windows 2000 Cygwin bash version "2.05b.0(9)" My application is a combination of Fortran and C. In Fortran Stdout's number is 6. When I ran the application from the Cygwin console it is giving the problem and exited. where there is a write statement to the stdout. ************************************************* Input/Output Error 179: Bad file descriptor In Procedure: openwt At Line: 562 Statement: Formatted WRITE Unit: 6 Connected To: Stdin End of diagnostics ************************************************* And then I typed the command "bash" (gone into one more level deeper), then it worked. And tried again one more step deeper ($SHLVL = 3) it gave the same problem. I kept on going deeper and deeper and my observation is... For all odd SHLVL values it is failing(giving the above error message) For all even SHLVL values it is succeeding. The strange thing is when I ran from the remote shell. My "rsh" shell is set to use "/usr/bin/bash" I ran the application on remote shell (using rsh) then the application is running properly. In all levels of SHLVL, it is running properly. Can you please suggest us a solution to solve this problem? Thanks, Vasudeva. -- 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/