Doug Gregor wrote:
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 :(
I ran this test compiled against both boost 1.31 and boost 1.32 and it appeared to work fine in both (had lots of output that I didn't sift through, I assumed I would have received a failed message if it didn't work). Thanks for trying. I'll take a look at this program and see if there's anything I can do to make it break. I definitely didn't get anywhere with my own test programs. Neal