> Hi,
> I had the same problem...
>
> This problem was fixed in the next release (1.40)
> Regards,
> Damien.
Ok I tried this and found:
a/ whereas 1.39 serialisation compiles with out _any_ warnings.
1.40 has a _blizzard_ sorry I meant avalanche of warnings
on building boost and on my application of the kind:
/var/tmp/ma0/boost/boost_1_40_0/boost/archive/basic_binary_oarchive.hpp:88: warning: comparison between signed and unsigned integer expressions
This makes it extremely difficult to see my own warnings.
Is 1.40 really production quality ?
We have a policy of no warnings, so the obvious question now,
is what release are these warning's fixed ?
b/ Still get the same crash on program exit.
Program received signal SIGSEGV, Segmentation fault.
0xb7ce3a08 in strcmp () from /lib/libc.so.6
(gdb) bt
#0 0xb7ce3a08 in strcmp () from /lib/libc.so.6
#1 0x083c814d in boost::serialization::extended_type_info::key_unregister ()
#2 0x083c8407 in boost::serialization::extended_type_info::~extended_type_info ()
#3 0x081bf8cc in ~extended_type_info_typeid (this=0x8789604) at /var/tmp/ma0/boost/boost_1_40_0/boost/serialization/extended_type_info_typeid.hpp:80
#4 0x081bf98e in ~singleton_wrapper (this=0x8789604) at /var/tmp/ma0/boost/boost_1_40_0/boost/serialization/singleton.hpp:104
#5 0x0819f508 in __tcf_25 () at /var/tmp/ma0/boost/boost_1_40_0/boost/serialization/singleton.hpp:121
#6 0xb7ca3599 in exit () from /lib/libc.so.6
#7 0xb7c8cfe8 in __libc_start_main () from /lib/libc.so.6
#8 0x08053921 in _start ()
Oh well! I will have to go back placing all the serialisation in one translation unit
and stick with 1.39.
Best regards,
Ta,
Avi