Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

RE: TERMCAP problem.



> Here is the backtrace.  If you want, I can also send you the core file.
> #0  0xef5a4274 in strcmp () from /usr/lib/libc.so.1
> #1  0x126c00 in tgetent (bp=0x0, name=0x15c2e8 "xterm") at termcap.c:469
> #2  0x48608 in init_term () at init.c:478
> #3  0x6f808 in termsetfn (pm=0x145e20, x=0x15c2e8 "xterm") at params.c:2763
> #4  0x6c514 in setstrvalue (v=0xefffed28, val=0x15c2e8 "xterm") at
> params.c:1513
>
> #5  0x6d7d0 in setsparam (s=0xeffffe45 "", val=0x15c2e8 "xterm") at
> params.c:1810
> #6  0x6767c in createparamtable () at params.c:515
> #7  0x491d0 in setupvals () at init.c:715
> #8  0x12158 in main (argc=1, argv=0xeffff4ac) at ./main.c:78
>

This strcmp() is in library function tgetent. Try to unset
TGETENT_ACCEPTS_NULL, recompile and try again. It is possible that your OS
actually needs preallocated buffer.

One more possibilty is, that screen creates too long termcap entry. IIRC I've
seen something similar. How long is new termcap entry? I think, common limit
is 1024.

-andrej



Messages sorted by: Reverse Date, Date, Thread, Author