From: John Maddock (john_at_[hidden])
Date: 2007-11-23 04:12:50
Gennadiy Rozental wrote:
> The link now shows boost::thread_resource_error as a thrown
> exception. I am afraid I would have problems figuring this out even
> if it was boost.test exception. I need an access to the platform to
> debug it. The only thing I can tell immediately is that system_error is
> caught by
> execution_monitor itself (see line ~ execution_monitor.ipp:1110). So
> it should be some strange combination of events to produce
> system_error from execution monitor invocation
Yep, these exceptions seem to be comming and going, which is rather
frustrating to say the least. Currently this one: http://tinyurl.com/3xx3o7
terminate called after throwing an instance of 'boost::system_error'
EXIT STATUS: 134
So the exception is raised even before cpp_main is entered and before
execution monitor's own try...catch blocks are entered I assume?
Noel: I don't suppose you have a couple of spare minutes to find out where
this exception is comming from?
Many thanks, John Maddock.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk