On 2024-04-06, Страхиња Радић <contact@strahinja.org> wrote:
> Дана 24/04/06 02:42PM, Eivind Eide написа:
>> tmux: vfprintf %s NULL in "%.*s"
>> bash: vfprintf %s NULL in "%.*s"
>> multitail: vfprintf %s NULL in "%.*s"
>> vim: vfprintf %s NULL in "%.*s"
>
> This happens in OpenBSD when a program passes NULL pointer to *printf family of
> functions. The bug reports should be directed upstream to individual packages.
The fact that these all started hitting this with the same printf string
(including tmux, which is in base) makes me wonder if it's coming from a
library, the most likely being libcurses which was updated between 7.4
and 7.5 (which all of those use).
Try to ascertain what's going on when that message is logged. ktrace
might give some clues.
Alternatively try to identify what's triggering it (this isn't normal -
I don't recall ever seeing that from tmux/vim myself) - could be an
environment variable. Can you reproduce it if you reset the environment
(env -i)? How about if you use a different TERM?
No comments:
Post a Comment