Michal Rokos schrieb: > If anybody could think of some better define than BROKEN_VSNPRINTF, I'm all > ears. CLUELESS_OVERFLOWN_VSNPRINTF? Because we have the same issue on Windows where vsnprintf returns -1 on overflow. But there is also another complication: The size parameter of the system's vsnprintf must not count the trailing NUL, i.e. the buffer must actually have space for one extra byte, whereas the POSIX version must count NUL. Can you check whether your vsnprintf has this flaw, too? If it doesn't, we would need another configuration variable so that we can distinguish these two kinds of brokenness. -- Hannes -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
