|author||Pablo Neira Ayuso <firstname.lastname@example.org>||2011-05-19 08:55:32 +0200|
|committer||Harald Welte <email@example.com>||2011-05-19 08:55:32 +0200|
logging: fix corrupted output
Harald reported a problem in the logging: http://lists.osmocom.org/pipermail/openbsc/2011-May/002896.html Reverting 81e9636454294ae10ef9bc8bf149dd0248afce76 seems to fix the problem. However, that workaround looks ugly. Holger gives us another clue on what was wrong: http://lists.osmocom.org/pipermail/openbsc/2011-May/002905.html While digging in the manpage, I found this: "The functions vprintf(), vfprintf(), vsprintf(), vsnprintf() are equivalent to the functions printf(), fprintf(), sprintf(), snprintf(), respectively, except that they are called with a va_list instead of a variable number of arguments. These functions do not call the va_end macro. Consequently, the value of ap is undefined after the call. The application should call va_end(ap) itself afterwards."
Diffstat (limited to 'include/osmocom/core/gsmtap_util.h')
0 files changed, 0 insertions, 0 deletions