Not sure I got you right. Do you mean catching exception somewhere top level and then showing stack of the original throw point? Isnt it stored (sorry, it was a long time ago) in EXCEPTION_POINTERS' member ContextRecord? AFAIR, if you use __try and __except and pass expression to __except with GetExceptionInformation() you are good to extract the original location of the exception (apparently unhandled) be it C++ or structured exception. Again, AFAIR, the only compiler option you have to set is /SEH -----Original Message----- From: Boost-users [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Gavin Lambert Sent: Tuesday, June 21, 2016 11:43 AM To: boost-users@lists.boost.org Subject: Re: [Boost-users] [boost] Checking interest in stacktrace library On 21/06/2016 15:51, Ernest Zaslavsky wrote:
If you're on Windows you have dbghelp Win32 functions which are no black art and quite straight forward to use.
Those will generate a stack trace from the current location of a given thread (usually the current thread). That's fine, but not what I was referring to. I meant extracting the stack trace of the original throw point from some place that catches an exception (possibly a top-level uncaught exception handler). That's the black art. It requires either cooperation of the throw point or delving into compiler-specific internals. _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users