On Thu, Jun 06, 2013 at 08:05:46PM +0200, Sven Joachim wrote: > On 2013-06-06 03:10 +0200, Thomas Dickey wrote: > > > On Wed, Jun 05, 2013 at 07:24:53PM +0200, Sven Joachim wrote: > >> No wonder that it segfaults, but why cur_term has these bogus values??? > >> you're the expert. :-) > > > > partly a blunder of course: I was fixing warnings from Coverity advising > > of a memory leak. Here's a fix. > > Works for me, thanks. :-)
no problem (will be part of tomorrow's patch).
For the terminfo entry itself, I can see the cause of the warning messages
that I mentioned. Using infocmp -1f, see
sgr=\E[0
%?
%p1%p6%|
%t;1
%;
%?
%p2%|
%t;4
%;
%?
%p4%|
%t;5
%;
%?
%p5%|
%t;2
%;
m,
The "%|" after p2, p4, p5 should be removed, since it OR's the top two items
on the stack. But there is only one. ncurses checks for that; other
implementations are likely to dump core.
--
Thomas E. Dickey <dic...@invisible-island.net>
http://invisible-island.net
ftp://invisible-island.net
signature.asc
Description: Digital signature
