Re: bash 2.04 possible TERM variable bug?

[Chet Ramey]

I wrote:

> >         $ 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).

Whoops.  I spoke too soon.  I am able to reproduce it with the current
development version of bash-2.05.  That's the good news.  The bad news
is that it's not bash that's freeing the memory twice.  Bash is allocating
it once and freeing it once.  The termcap library (specifically tgetent())
is freeing the memory out from underneath bash/readline.

I'm going to look at the Red Hat libtermcap sources and see if I can
discover what's happening.

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/