On Thu, Aug 8, 2013 at 5:19 PM, William ML Leslie < [email protected]> wrote:
> On 09/08/2013 7:57 AM, "David Jeske" <[email protected]> wrote: > > If we wish to preserve that stack for future handlers, no handler can be > allowed to set the stack pointer (unroll) unless it is ending the exception > propagation. > That's to strong. First, the backtrace printing mechanism isn't done in a handler. It's done deep in the runtime. Second, it's perfectly fine for unwind code to change the stack pointer. All we need to do to support the backtrace is to save the stack pointer that was current at the time of the most recent exception on that thread. If we're running code in a catch block or a finally block, we're no longer interested in a stack trace from the original raise. You guys are *way* over-thinking this.
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
