[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: user/581: `csh -n` causes an SIGSEGV
- To: bugs_(_at_)_cvs_(_dot_)_openbsd_(_dot_)_org
- Subject: Re: user/581: `csh -n` causes an SIGSEGV
- From: "Todd C. Miller" <Todd_(_dot_)_Miller_(_at_)_courtesan_(_dot_)_com>
- Date: Tue, 25 Aug 1998 10:20:01 -0600 (MDT)
- Reply-to: "Todd C. Miller" <Todd_(_dot_)_Miller_(_at_)_courtesan_(_dot_)_com>
The following reply was made to PR user/581; it has been noted by GNATS.
From: "Todd C. Miller" <Todd_(_dot_)_Miller_(_at_)_courtesan_(_dot_)_com>
To: josh_(_at_)_brightech_(_dot_)_net
Cc: gnats_(_at_)_openbsd_(_dot_)_org, josh_(_at_)_fixation_(_dot_)_com
Subject: Re: user/581: `csh -n` causes an SIGSEGV
Date: Tue, 25 Aug 1998 10:12:12 -0600
Hmm, I can't reproduce that on the 2.3 sparc release so I suspect
it is somehow specific to the script you are running through -n.
Do you get the core dump doing:
csh -n /usr/share/skel/dot.cshrc
Visit your host, monkey.org