[boost] [Serialization] Bizarre bug - reviewed

Subject: [boost] [Serialization] Bizarre bug - reviewed
From: Tobias Loew (Tobias.Loew_at_[hidden])
Date: 2013-01-17 11:45:57

I just came across the following bug
http://boost.2283326.n4.nabble.com/Serialization-Bizarre-bug-td2612558.html
and noticed that the bizarre behaviour is still reproducible (I used
boost-version 1.52). 
I could figure out that in the buggy build there is an additional static
initialization of the singlenton<T>::instance in
boost\serialization\singleton.hpp in line 149 at startup

>	serial_bug.exe!`dynamic initializer for
'boost::serialization::singleton<boost::archive::detail::pointer_oserializer&lt;boost::archive::text_oarchive,std::vector&lt;char,std::allocator&lt;char>
> > >::instance''()  Zeile 149	C++

which leads to a call of set_bpis in iserializer.hpp line 347. Thus,
std::vector<char> will be saved (but NOT loaded) through a pointer.

For apps that store and load the same types the problem usually does not
arise, but for server/clients this may not be the case (e.g. apps using the
RCF-library)

Tobias

--
View this message in context: http://boost.2283326.n4.nabble.com/Serialization-Bizarre-bug-reviewed-tp4641499.html
Sent from the Boost - Dev mailing list archive at Nabble.com.