Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!kailand.kai.com!pwolfe
From: pwolfe@kailand.kai.com (Patrick Wolfe)
Newsgroups: gnu.bash.bug
Subject: bash bug report
Message-ID: <8912030428.AA01426@kailand.kai.com>
Date: 3 Dec 89 04:28:13 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: Kuck and Associates, 1906 Fox Drive, Champaign IL USA 61820, voice 217-356-2288, fax 217-356-5199
Lines: 35

System:  Sequent Balance B8
OS:      Sequent Dynix (BSD 4.2)
version: 1.04

I picked up and started using bash this week and found a few problems.

First, there appears to be a bug in the malloc routines.  When I compiled bash
with the supplied malloc, it would die with "free: invalid argument" after
the following command sequence was executed:

	$ lf ~partial-username<tab>
	$ lf ~partial-username<tab>

The first command would work, but the second one would kill bash.  When I
recompiled using the system's malloc, everything seems to work okay.

The second problem is that readline seems to trash the command line if the
TERMCAP for the current terminal has the "IC" capability in it.  It is adding
one extra blank for every character inserted (including one for the asterisk at
the beginning of an edited line).

Also, bash allows multi line prompts, but readline has problems when one is
used, since it likes to jump to the begining of the current line and rewrite
the prompt and beginning of the command.

I would like to commend all those who've been working on bash and readline so
far.  I plan to continue using bash, and to try to find and fix any bugs I can.
The "vi mode" simply blows away TCSH.

-- 

        Patrick Wolfe
        System Manager, Kuck & Associates
	work: pwolfe@kailand.kai.com  or  uunet!kailand!pwolfe
	home: pat@pawnix.kai.com  or  uunet!kailand!pawnix!pat