[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bash 2.04 possible TERM variable bug?
From: |
Chet Ramey |
Subject: |
Re: bash 2.04 possible TERM variable bug? |
Date: |
Wed, 31 Jan 2001 17:19:07 -0500 |
> Machine Type: i386-redhat-linux-gnu
>
> Bash Version: 2.04
> Patch Level: 11
> Release Status: release
>
> Description:
> I have recently used bash remotely via a serial line. This
> requires me to often change the TERM variable, depending on the
> nature of the equipment on the other end of the line. I observed
> that setting the TERM variable to an invalid terminal type causes
> bash to abort.
>
> I have tested bash on this machine ('pepperoni.brooknet' - a machine
> on a private home network) and on a 400 MHz machine with an AMD K6-2.
> The OS on the other machine is Red Hat 7.0 as well - the bug appears
> there too.
>
> Repeat-By:
> [my comments in square brackets]
> $ echo $TERM
> vt220
> $ ls --color=auto -F
> [colorized ls listing appears]
> $ export TERM=-
> [invalid TERM setting]
> $ ls
> [ls output appears with no colors as tty setting is wrong]
> $ export TERM=vt220 [restored TERM setting to the default type]
> $ ls
> [ls output colorised again and all appears normal]
> $ export TERM=-
> [other values tried: TERM=vt220-mono, TERM=vt220-25]
> free: called with already freed block argument
> last command: export TERM=-
> Stopping myself...
> [bash exits]
I can't reproduce this on FreeBSD or Linux with the current development
version of bash-2.05, so I'm going to assume it's fixed. (I can reproduce
it on Linux with bash-2.04).
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet)
Chet Ramey, CWRU chet@po.CWRU.Edu http://cnswww.cns.cwru.edu/~chet/