1 Oct 02:37
Re: serialization 1.36.0 extended_type_info exitissue(s)
Robert Ramey <ramey <at> rrsd.com>
2008-10-01 00:37:06 GMT
2008-10-01 00:37:06 GMT
I'm doubting that its the complexity of the class.
More likely that its the "last" class.
Also it might be relevant that your using a multicore processor.
The library presumes that everything before entering main
and after leavnig main is run on a single thread. This seems
like a reasonable presumption to me. You might look into
this.
You should also run the test with break points set on
~singleton(){
m_is_destroyed = true; // <<< break here
}
To verify that this isn't getting called at an unexpected time.
Robert Ramey
Robert Mecklenburg wrote:
> Robert Ramey writes:
>> Its currently in the trunk - head version. I can't test it and
>> it doesn't fail on any test platforms, so its up to you guys
>> to test it.
>
> I checked out the trunk and tested some of my code. Of the five
> classes I tested, four unit tests now pass cleanly. One of them still
(Continue reading)
RSS Feed