On Fri, 24 Oct 2008, Allison Randal wrote: > Will Coleda wrote: > > Allison Randal wrote: > > > ...you expect 'rethrow' to keep the stack trace of the original 'die'? > > Yes. > > The way to do this is to add stack trace information to the Exception's > 'stacktrace' attribute when the exception is first thrown, and print that out > for an unhandled exception, instead of printing out the literal current path > of execution. (This is why I added the 'stacktrace' attribute.)
What about keeping track of where the exception was originally created? If we have lazy exceptions, then knowing where the fault they represent was detected is probably more important than were (exactly) it was triggered. Or does this all amount to the same thing? Is an exception only "lazy" because there's an enclosing dynamic scope that catches it and transmogrifies it into an Uncaught Exception? Or if not, could we have both back-traces available? A "created_by" back-trace and a "thrown_by" back-trace? -Martin
