$include_dir="/home/hyper-archives/boost-users/include"; include("$include_dir/msg-header.inc") ?>
From: Thorsten Ottosen (thorsten.ottosen_at_[hidden])
Date: 2008-08-11 06:57:40
Florian Winter skrev:
> When a debug version of a unit test application using Boost.Test crashes 
> on Windows, no popup appears that asks for attaching the debugger. 
> Instead, the process prints a stack dump to standard output and then 
> exits normally. Attaching the debugger before the process crashes does 
> not help.
> Is there any way to prevent Boost.Test from catching system errors such 
> as access violations (on Windows) and signals (on Linux and similar 
> platforms) so that conventional debuggers can be used?
> 
Gennadiy,
I have had similar problems with Boost.Test. I did manage to use the 
debugger, when I created the test application directly in visual studio 
and added the parameters, but I have been unable to get the same 
behavior when compiling via bjam fro visual slick-edit.
IMO, it should be dead-simple to do this. Can we be given a little help?
Thanks
-Thorsten