From owner-freebsd-bugs  Mon Jun 19 23:22:03 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id XAA28678
          for bugs-outgoing; Mon, 19 Jun 1995 23:22:03 -0700
Received: from balboa.eng.uci.edu (balboa.eng.uci.edu [128.200.61.2])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id XAA28672
          for <freebsd-bugs@freebsd.org>; Mon, 19 Jun 1995 23:22:01 -0700
Received: from localhost.uci.edu by balboa.eng.uci.edu with SMTP id AA21591
  (5.65c/IDA-1.4.4 for freebsd-bugs@freebsd.org); Mon, 19 Jun 1995 23:21:53 -0700
Message-Id: <199506200621.AA21591@balboa.eng.uci.edu>
To: freebsd-bugs@freebsd.org
Subject: FreeBSD 1.0 incompatability
Date: Mon, 19 Jun 1995 23:21:52 -0700
From: Steven Wallace <swallace@balboa.eng.uci.edu>
Sender: bugs-owner@freebsd.org
Precedence: bulk


The tcsh for FreeBSD 1.0 that has worked great for me for the longest
time now seg faults in FreeBSD 2.0.5.  It only faults if I telnet
or rlogin and use the shell.  If I use an xterm there is no problem with
it.  The 2.0.5 tcsh works fine in both cases.

The corefile gives me this info:

(gdb) where
#0  0x455c3d34 in ?? ()
Cannot access memory at address 0x6b3a524f.

Use the tcsh on the 1.0 CDROM.

Steven