Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!MARYS.MIT.EDU!ccount
From: ccount@MARYS.MIT.EDU (Craig A. Counterman)
Newsgroups: gnu.bash.bug
Subject: Re: Ultrix 3.0 if date: yes, it's there
Message-ID: <17741.613859561@marys.MIT.EDU>
Date: 14 Jun 89 20:32:41 GMT
References: <8906141744.AA00311@life.ai.mit.edu>
Sender: bob@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 25


|>> Date: Wed, 14 Jun 89 12:48:10 EDT
|>> From: Andrew Thomas <andrewt@watsnew.waterloo.edu>
|>> To: bug-bash@prep.ai.mit.edu
|>> Subject: A set of bash bugs and suggestions (long)
|>> 
|>> composer@bu-cs.bu.edu writes:
|>>  > |   Date: Tue, 13 Jun 89 14:33:53 -0400
|>>  > |   From: James J Dempsey <jjd@bbn.com>
|>>  > |
|>>  > |   I am using Bash 0.99 under Ultrix 3.0 on a VAX 8530.
|>>  > |
|>>  > |   There seems to be a bad interaction with the use of PROMPT_COMMAND and
|>>  > |   "if".  Consider the following:
|>>  > |

 ....

|It seems that no one can reproduce this, although I haven't seen a
|message from anyone running Ultrix 3.0.  Here is some more data to aid
|in debugging.

I can reproduce it on Ultrix 3.0 on a MicroVAX II.  It just core dumps.

Craig