Boost Users :
Subject: Re: [Boost-users] [Repost][Boost][Serialization] ASSERT triggeredduring reading 1.40 binary archive w/ Boost 1.47
From: Pfligersdorffer, Christian (Christian.Pfligersdorffer_at_[hidden])
Date: 2011-08-03 02:01:43
We were facing similar problems jumping from 1.36 to 1.45.
Binary archive backwards compatibility is broken in a few places.
But: it is fixable. We may provide a patch - is there a TRAK ticket?
-- Christian Pfligersdorffer Software Engineering www.eos.info > -----Ursprüngliche Nachricht----- > Von: boost-users-bounces_at_[hidden] [mailto:boost-users-bounces_at_[hidden]] Im Auftrag von > Marc Perso > Gesendet: Mittwoch, 3. August 2011 07:30 > An: boost-users_at_[hidden] > Betreff: [Boost-users] [Repost][Boost][Serialization] ASSERT triggeredduring reading 1.40 binary archive > w/ Boost 1.47 > > Let me forward this message posted few days ago since nobody has confirmed > that the issue described hereafter exists. I would really appreciate if > someone could take a look (maybe Mr Robert Ramey) and give some advice on > this subject. > > Best regards, > > Marc Viala > > ------------------------------------------------------------------------ > > Hello Booster, > > We are trying to jump from Boost 1.40 to Boost 1.47 but we are facing an > issue: an ASSERT is raised in debug mode when reading back binary archive > generated by Boost.Serialization 1.40 with the Boost.Serialization 1.47. > This ASSERT is at line 116 in basic_archive.hpp: > > BOOST_ASSERT(t_ <= boost::integer_traits<base_type>::const_max) > > And it occurs with the following platform: MSVC 8.0 and Windows XP/32bits or > Win7/64bits. > > Looking at the load_override and save_override implementations for > class_id_type in #1.40, they seem loading and saving an 'int_least16_t' > (equiv. to a short for our platform) while load_override(class_id_type) for > #1.47 attempts to read an 'int' (file: basic_binary_iarchive.hpp @ line 98). > > My questions are: > - This assert suggests that we can't read back previous binary archives > (#1.40 at least) with Boost.Serialization 1.47, is this a known pending > issue for Boost.Serialization? > > - If yes, how we can manage that and how we can complete the migration to > 1.47 in our case (it should be noted that we must be able to read back our > 1.40 binary archives)? Is there any known patch for this problem? > > Any assistance will be greatly appreciated. > > Best regards, > > Marc Viala > > PS: I'm not sure but ticket #5567 seems already opened on this issue but has > not been yet fixed (https://svn.boost.org/trac/boost/ticket/5567). > > > > _______________________________________________ > Boost-users mailing list > Boost-users_at_[hidden] > http://lists.boost.org/mailman/listinfo.cgi/boost-users
Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net