Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!BBN.COM!jjd
From: jjd@BBN.COM (James J Dempsey)
Newsgroups: gnu.bash.bug
Subject: Re: A set of bash bugs and suggestions (long)
Message-ID: <8906141744.AA00311@life.ai.mit.edu>
Date: 14 Jun 89 17:34:54 GMT
References: <8906141648.AA21706@watsnew.waterloo.edu>
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 88

>> 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:
>>  > |
>>  > |   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

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.

Below is the output of a bash session where I tried to reduce my
environment to the absolute minimum.  Also included is the output of
"set" to show the environment.  It is interesting to note that it
didn't say "Bad command type" this time.

		--Jim Dempsey--
		BBN Communications
		jjd@bbn.com (ARPA Internet)
                ..!{decvax, harvard, wjh12, linus}!bbn!jjd


% bash -norc
bash$ set
EUID=14895
UID=14895
HISTSIZE=500
HISTFILE=/u1/jjd/.bash_history
BASH_VERSION=0.99
BASH=/usr/local/gnu/bin/bash
SHLVL=1
PWD=/u1/jjd
MAILPATH=/usr/spool/mail/jjd
MAILCHECK=60
IFS= 	

PS2=bash>
PS1=bash$ 
TERMCAP=emacs:co#80:tc=unknown:
PATH=:/u1/jjd/Bin:/usr/local/gnu/bin:/nd/bin:/usr/local/bin:/usr/local/nosupport:/usr/ucb:/usr/bin:/bin:/u1/ezf/bin:/usr/local/bin/X11:/usr/local/bin/X10.4:/usr/local/bin/uw:/u1/jjd
USER=jjd
TERM=emacs
SHELL=/usr/local/gnu/bin/bash
HOME=/u1/jjd
bash$ if date
bash>then
bash>echo fine
bash>fi
Wed Jun 14 13:26:05 EDT 1989
fine
bash$ PROMPT_COMMAND=date
Wed Jun 14 13:26:15 EDT 1989
bash$ if date
Wed Jun 14 13:26:54 EDT 1989
bash>then
Wed Jun 14 13:26:55 EDT 1989
bash>echo fine
Wed Jun 14 13:26:56 EDT 1989
bash>fi
Illegal instruction (core dumped)
%