On Mon, 15 Apr 2024 14:17:10 +0200, =?utf-8?B?0KHRgtGA0LDRhdC40ZrQsCDQoNCw0LTQu
NGb?= wrote:
> Just to clarify, this particular instance of this issue seems to be related t
> o
> terminfo.
>
> In general, as I stated earlier, the log message
>
> ... [program_name]: vfprintf %s NULL in "[format_string]"
>
> is output whenever NULL is passed to the *printf family of functions. That
> could be vfprintf, but also printf, fprintf, sprintf... and so on and so fort
> h.
> The inconvenient part of this otherwise very useful mechanism of detecting
> incorrect code is that there is no precise indication of the location in the
> source code which is incorrectly written in this manner. It could be the
> program itself, or it could be one of the libraries it uses, as is likely the
> case here. The only clue is the format string in the message, which could be
> not distinctive enough.
I believe this is fixed by:
CVSROOT: /cvs
Module name: src
Changes by: mill...@cvs.openbsd.org 2024/04/12 08:10:28
Modified files:
lib/libcurses/tinfo: read_entry.c
Log message:
Avoid snprintf() of NULL when _nc_get_source() returns NULL.
The filename buffer is not actually used in this case but it is
safer to set it to the empty string than to leave it uninitialized.
OK tb@
