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 Message-Id: Date: Thu, 18 Mar 2004 13:46:22 -0700 From: "Aaron Humphrey" To: Subject: Re: Cygwin shells exit immediately Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i2IKiTCh025487 Igor Pechtchanski wrote: > Did you try running bash non-interactively with a long-running command, > e.g., 'bash -c "sleep 20"'? Does that work? It doesn't return an error, but it doesn't take any more or less time to return than bash -c "sleep 1" or bash -c "sleep 150" > Does 'bash --norc -i' work? It doesn't do anything different. I put an "echo" into my .bashrc, so I can tell whether it's being sourced or not, but it doesn't seem to make any difference. Whether it is or not, bash still exits. > Also, if vim works, try adding the following to your .bashrc: > set -o ignoreeof > to eliminate the possibility of stray EOFs being sent to bash... No luck there. > If all else fails, there's always strace, but it will involve some effort > on your part to examine it and try to figure out why bash exits. I have a strace from my coworker's machine, where bash still works. Unfortunately, they both seem to end, at least, the same way: 255 166507 [main] bash 2872 readv: readv (0, 0x22E6C0, 1) blocking, sigcatchers 1 52 166559 [main] bash 2872 readv: no need to call ready_for_read So if there's a problem, it comes earlier. I'm going to try reinstalling and seeing if that works. --Aaron V. Humphrey Kakari Systems, Ltd. -- 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/