<a name="boost_test.practical_usage_recommendations.command_line_usage_recommendatio.h0"></a>
<span class="phrase"><a name="boost_test.practical_usage_recommendations.command_line_usage_recommendatio.if_you_got_fatal_exception_somew"></a></span><a class="link" href="command_line_usage_recommendatio.html#boost_test.practical_usage_recommendations.command_line_usage_recommendatio.if_you_got_fatal_exception_somew">If
you got fatal exception somewhere within test case, make program generate
- coredump by adding extra command line argument</a>
+ core-dump by adding extra command line argument</a>
</h5>
<p>
If you got "memory access violation" message (or any other message
</pre>
<p>
to the test run command line. Now run the test again and it will create a
- coredump you could analyze using you preferable debugger. Or run it under
+ core-dump you could analyze using you preferable debugger. Or run it under
debugger in a first place and it will break at the point of failure.
</p>
<h5>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2001-2018 Boost.Test contributors<p>
+<td align="right"><div class="copyright-footer">Copyright © 2001-2019 Boost.Test
+ contributors<p>
Distributed under the Boost Software License, Version 1.0. (See accompanying
file LICENSE_1_0.txt or copy at <a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)
</p>