[Boost-testing] [boost][test]Infinite loop due to recent change?

Subject: [Boost-testing] [boost][test]Infinite loop due to recent change?
From: Belcourt, Kenneth (kbelco_at_[hidden])
Date: 2010-05-18 17:12:04

Hi,

The Sandia Darwin Intel testers have been stable for some time but a  
recent change seems to have broken the tester.  This test in  
Boost.Test, seems to be the source of the problem (test_tools_test).

brisc: kbelco$ pwd
/Volumes/Scratch/kbelco/boost/results/boost/bin.v2/libs/test/test/ 
test_tools_test.test/intel-darwin-11.0/debug

brisc: kbelco$ more test_tools_test.output
terminate called after throwing an instance of 'boost::system_error'
Running 22 test cases...
terminate called recursively
terminate called recursively
terminate called recursively
terminate called recursively
[  this message repeated until the test timed out after 5 minutes ]

The test output file size is 260Mb.

-rw-r--r--  1 kbelco  SANDIA\domain users  262252256 May 18 14:13  
test_tools_test.output

This problem causes process_jam_log to loop indefinitely trying to  
digest this enormous output file.  Could Gennadiy or anyone else  
please take a look and see if there's a way to stop the infinite  
looping of "terminate called recursively".

Thanks.

-- Noel