Re: [Boost-users] serialization 1.36.0 extended_type_info exit issue(s)

Subject: Re: [Boost-users] serialization 1.36.0 extended_type_info exit issue(s)
From: Hartmut Kaiser (hartmut.kaiser_at_[hidden])
Date: 2008-10-08 14:00:17

> Robert Mecklenburg, I'd be interested to see what you get from
> running your tests under valgrind like this:
> 
>    valgrind --tool=memcheck --malloc-fill=FF --free-fill=EE
> ./my_failing_test
> 
> Specifically
> 
> - what happens while all the global statics are being destroyed
> - Can you get a test that passes when run 'normally' to fail when run
>    under valgrind as above?
> 
> I've been chasing this for a few days and it just got away from me
> for the third or fourth time.  It looks like there are some
> double-deletes around and I wouldn't be surprised if it were a
> compiler or std library bug.  I can come up with one only one
> (lame) question so far...  why are the key_unregister methods
> of the extended_type_info classes written like this:

In my experience this happens whenever you BOOST_CLASS_EXPORT() a specific
type more than once.

Regards Hartmut