Given
logger foo;xterm -tn xterm-256color -e ktrace -di /bin/ksh
the log message 'ksh: vfprintf %s NULL in "%.*s"' appears when
~/.terminfo/x/xterm/xterm-256color does not exist.
The log message no longer appears after running
cp /usr/share/terminfo/x/xterm-256color ~/.terminfo/x/
and comes back after deleting the ~/.terminfo/x/xterm-256color file.
The kdump when the log message happens runs along the lines of:
79510 ksh CALL access(0x744b97b272e0,0x4<R_OK>)
79510 ksh NAMI "/home/jmates/.terminfo/x/xterm-256color"
79510 ksh RET access -1 errno 2 No such file or directory
79510 ksh CALL issetugid()
79510 ksh RET issetugid 0
79510 ksh CALL issetugid()
79510 ksh RET issetugid 0
79510 ksh CALL issetugid()
79510 ksh RET issetugid 0
79510 ksh CALL open(0x744b97b1b600,0x10000<O_RDONLY|O_CLOEXEC>)
79510 ksh NAMI "none.db"
79510 ksh RET open -1 errno 2 No such file or directory
79510 ksh CALL mprotect(0x4e89f6c1000,0x1000,0x3<PROT_READ|PROT_WRITE>)
79510 ksh RET mprotect 0
79510 ksh CALL mprotect(0x4e89f6c1000,0x1000,0x1<PROT_READ>)
79510 ksh RET mprotect 0
79510 ksh CALL open(0x744b97b1eed0,0x10000<O_RDONLY|O_CLOEXEC>)
79510 ksh NAMI "none"
79510 ksh RET open -1 errno 2 No such file or directory
79510 ksh CALL sendsyslog(0x744b97b1c140,35,0<>)
79510 ksh GIO fd -1 wrote 35 bytes
"<10>ksh: vfprintf %s NULL in "%.*s""
79510 ksh RET sendsyslog 0
