On Mar 3, 2013, at 9:02 AM, Edward Diener <eldiener@tropicsoft.com> wrote:
On 3/3/2013 6:56 AM, Mathias Gaunard wrote:
On 03/03/13 10:54, Artyom Beilis wrote:
Generally it is very interesting topic and very useful stuff (from my experience in deploy with CppCMS).
While it is interesting, I have not found it to be that useful in practice. The debugger already does all of this better that you could ever do yourself.
It is probably a better idea to integrate your app with a debugger than to rewrite a debugger inside your app.
I believe there are valid uses for displaying a backtrace at points in the code where you do not want to have to stop the debugger simply to be able to visually view the backtrace ( as a call stack ). So I would look forward to a Boost cross-platform library which allowed a programmer to output the backtrace through code.
The example of this that has been proposed in the past is to automatically log the call stack on allocations/deallocations/exceptions. Alternately, to attach the call stack to exceptions before they were thrown (Boost.Exception set up to allow people to attach arbitrary data to an exception). -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki