On Dec 15, 2004, at 5:40 PM, Doug Gregor wrote:
On Dec 6, 2004, at 4:03 PM, Neal Coombes wrote:
I have been experiencing some strange behaviour (on Solaris 2.9 intel) with the signals::trackable object. I'm using it on all my objects that connect to signals and it doesn't seem to disconnect the signals consistently on destroyed objects (these objects are publicly and virtually derived from trackable). I've worked around the problem by manually disconnecting from all signals in the objects destructors.
I'm having a very hard time making a small example program to demonstrate this behaviour (but I am working on it :). In the meantime if anyone else has experienced this kind of behaviour or has any information that might help, it would be greatly appreciated.
I now have a test case that exhibits the problem and am looking into the problem.
Doug
Scratch that. I _don't_ have a test case that exhibits the problem. Even the signals torture test (random_signal_system) isn't detecting any problems. *If* you have some spare time, it might help if you could build the random_signal_system test (in libs/signals/test) from CVS and run it as ./random_signal_system 500 0.01 10000 If the final BOOST_TEST doesn't throw, then we haven't duplicated the problem :( Doug