From: Greg Colvin (gregory.colvin_at_[hidden])
Date: 2003-03-19 19:50:44
std::exception once had a where() member for this purpose, but it
didn't survive.
Without runtime library support it will be difficult to do, but not
impossible --
the Oracle runtime has platform-specific code for capturing the stack
trace on all
the of the many platforms we support. I can't post the code, but could
tell how it
is done on platforms of interest to Boost.
On Wednesday, Mar 19, 2003, at 17:17 America/Denver, Darren Cook wrote:
>> I would love boost to provide an exception class/framework/something
>> with this capability to encourage collection of context information,
>> which would make problem diagnosis so much easier.
>> Perhaps I could relate some of my experience and put some ideas up
>> for discussion?
>
> I'm interested (in fact I nearly posted a message yesterday asking if
> there was already anything that did this).
>
> I wanted something like the call stack that shows in python or java
> when an uncaught exception occurs; if you're also suggesting a
> snapshot of local vars/parameters then I'll be in heaven and may never
> need to fire up a debugger again :-).
>
> Darren
>
>
> _______________________________________________
> Unsubscribe & other changes:
> http://listarchives.boost.org/mailman/listinfo.cgi/boost