Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!WATSNEW.WATERLOO.EDU!andrewt
From: andrewt@WATSNEW.WATERLOO.EDU (Andrew Thomas)
Newsgroups: gnu.bash.bug
Subject: A set of bash bugs and suggestions (long)
Message-ID: <8906141648.AA21706@watsnew.waterloo.edu>
Date: 14 Jun 89 16:48:10 GMT
References: <8906132121.AA04301@bucse.bu.edu>
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 31

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.
 > |
 > |		       ------------------------------
 > |   bug:
 > |
 > |   There seems to be a bad interaction with the use of PROMPT_COMMAND and
 > |   "if".  Consider the following:
 > |
 > |   if date
 > |   then
 > |       echo yes
 > |   fi
 > |
 > |   This works fine if PROMPT_COMMAND is unset, but if PROMPT_COMMAND is
 > |   set to (say) "date", then bash core dumps after saying something like:
 > |   "OOPS!  Bad command type `313548'!"
 > 
 > Well, I don't have an Ultrix system to play with right now.  But, I was
 > unable to reproduce the above core dump on a Sun 3 running Sun UNIX 4.2
 > Release 3.4 nor on an Encore Multimax running UMAX 3.3.  Can anyone else
 > out there duplicate this problem?

I am running Ultrix 2.0 on a uVaxII.  I tried to reproduce this on a
clean bash session, and could not do it.

Andrew Thomas
andrewt@watsnew.waterloo.edu	Systems Design Eng.	University of Waterloo