On 10 January 2012 11:16, Mathias Gaunard <mathias.gaunard@ens-lyon.org>wrote:
On 01/10/2012 04:29 PM, Marshall Clow wrote:
On Jan 10, 2012, at 7:11 AM, Artyom Beilis wrote:
Boost.StackTrace
Collecting stack trace automatically from exception and printing it.
Very Very useful for debugging.
http://cppcms.sourceforge.net/**cppcms_ref_v0_99/** namespacebooster_1_1stack__**trace.html<http://cppcms.sourceforge.net/cppcms_ref_v0_99/namespacebooster_1_1stack__trace.html> http://cppcms.sourceforge.net/**cppcms_ref_v0_99/backtrace_8h_** source.html<http://cppcms.sourceforge.net/cppcms_ref_v0_99/backtrace_8h_source.html>
Any interest in this library. It works (collects a trace and prints it) on: Windows, Solaris, Linux, Mac OS X
This would be a great (feature) addition for Boost.Exception; the ability to attach a stack trace to an exception showing where it was thrown.
Extremely useful. We make extensive use of in house 'developed' (i.e. assembled from myriads small snippets on the web) stacktrace classes.
As you say, very, very useful for debugging
Why not just use a debugger?
They can give backtraces as well.
It's for when you don't have a debugger attached, or don't want to stop your program from continued execution: * To log callstacks from a running program doesn't infer (very much) with its execution, such as would halting it. For large systems more powerful than debugging. * Production (server) environments can't be halted and debugged due to an exception, but retrieving the stacktrace will aid in later error analysis. - Christian