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... :-)
Works as expected in 7.1.