Bug 41410 - tcsh reports freeing memory below the bottom of memory from setenv TERM
tcsh reports freeing memory below the bottom of memory from setenv TERM
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: libtermcap (Show other bugs)
6.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-05-20 01:17 EDT by Nancy Fudd
Modified: 2007-04-18 12:33 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-05-20 01:17:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nancy Fudd 2001-05-20 01:17:43 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.4 i686)

Description of problem:
(initially I thought this was a tcsh problem)
Start tcsh
setenv TERM :0.0
setenv TERM vt100
 free(8098140) below bottom of memory. (memtop = 8155c00 membot = 80bd380)

How reproducible:
Always

Steps to Reproduce:
1. Start tcsh
2. Type 'setenv TERM :0.0'
3. Type 'setenv TERM vt100'
This is with tcsh-6.10-0.6.x and libtermcap-2.0.8-20

Actual Results: 
# setenv TERM :0.0
tcsh: No entry for terminal type ":0.0"
tcsh: using dumb terminal settings.
# setenv TERM vt100
free(8098140) below bottom of memory. (memtop = 811d400 membot = 80bd380)
#


free(8098140) below bottom of memory. (memtop = 8155c00 membot = 80bd380)


Expected Results:  No error should have been generated.

Additional info:

I've reproduced it on several redhat 6.2 systems, but not on slackware nor
on redhat 6.1

Also, as you can see, the first 'setenv' is just a typo (er, 'thinko').  It
doesn't have to be ':0.0'; I tried it successfully with '0' and ':', same
error.

The output of 'ldd' on the unaffected redhat 6.1 system is identical to the
output of 'ldd' on the affected redhat 6.2 systems.

The output of 'md5sum' on the libraries reported by 'ldd' show that
libtermcap is different.

The output of 'rpm -q -a | grep libtermcap' shows that there are two
different versions of termcap:
  libtermcap-2.0.8-13    -- working
  libtermcap-2.0.8-20     -- not working

Congratulations, it looks like you've added a bug... now, could you please
remove it?
Thanks!  :-)

It doesn't seem to be a severe problem, but anytime a program has memory
problems it makes a person worry that 'buffer overflow' may not be far
behind... :-)
Comment 1 Bernhard Rosenkraenzer 2001-05-20 05:59:39 EDT
Works as expected in 7.1.

Note You need to log in before you can comment on or make changes to this bug.