I don't know what the constraints are.
But serialization 1.36 was tested against the rest
of boost 1.35. So, Just changing the
serialization directories to boost 1.36 (or 1.37)
and rebuilding would work.
Robert Ramey
Thanks Guys!
I verified your analysis by adding virtual destructor to polymorphic
oarchive and mem leak vanished as expected.
Currently due to some constraints I cannot move to boost 1.36.
In that case, do you think it's sufficient to just add these virtual
destructors ?
Or there are some other significant fixes related to serialization which
also need to be merged from 1.35 code base?
-Sameer
On 12/3/08, Kim
Barrett <kab.conundrums@verizon.net>
wrote:
At 10:42 AM +0530 12/3/08, sam p wrote:
But
if I modify below given code as given below then it doesn't show any
memory leak.
I am using boost 1.32.
The
virtual destructor for polymorphic_oarchive (and iarchive) was
added
relatively recently, I think in boost 1.35.
_______________________________________________
Boost-users mailing
list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users