You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this intentional? According to my understanding of the C standard it is undefined behavior if va_end() is missing after va_start() has been called. See for example ISO/IEC 9899:TC3:
7.15.1 Variable argument list access macros
...
Each invocation of the va_start and va_copy macros shall be matched by a corresponding invocation of the va_end macro in the same function.
...
7.15.1.3 The va_end macro
...
If there is no corresponding invocation of the va_start or va_copy macro, or if the va_end macro is not invoked before the return, the behavior is undefined.
The text was updated successfully, but these errors were encountered:
I stumbled over two places in the serialization code where
va_start()
is called without a corresponding call tova_end()
:serialization/include/boost/serialization/extended_type_info_no_rtti.hpp
Line 130 in 3f322d4
serialization/include/boost/serialization/extended_type_info_typeid.hpp
Line 116 in 3f322d4
Is this intentional? According to my understanding of the C standard it is undefined behavior if
va_end()
is missing afterva_start()
has been called. See for example ISO/IEC 9899:TC3:The text was updated successfully, but these errors were encountered: