Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Tue, 20 Aug 2002 18:55:35 -0500 (Central Daylight Time)
From:	Michael Hoffman <grouse AT mail DOT utexas DOT edu>
Subject:	Re: bash segmentation fault under rxvt
In-reply-to:	<200208201412.g7KECft15116@wolf.cimsoft.com>
X-X-Sender:	grouse AT mail DOT utexas DOT edu
To:	cygwin AT cygwin DOT com
Message-id:	<Pine.WNT.4.44.0208201850030.724-100000@barbecueworld>
MIME-version:	1.0

On Tue, 20 Aug 2002, Robert Mecklenburg wrote:

> When I start bash in an rxvt window and type C-<up arrow> the rxvt
> window terminates.  If I perform the same operation within a
> recursively invoked bash the message: "Segmentation fault" is printed
> and the inner most shell exits.  If I run the bash shell from a dos
> window I get a simple beep instead of a seg fault.

I get this too. Except that when I type C-<up arrow> in bash running on
the console, it is the same behavior as just <up arrow>.

CYGWIN_NT-5.1 BARBECUEWORLD 1.3.12(0.54/3/2) 2002-07-06 02:16 i586 unknown
-- 
Michael Hoffman <grouse AT mail DOT utexas DOT edu>
The University of Texas at Austin


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -