Hi Carl,
On Jul 24, 3:25 pm, cgay <carl...@gmail.com> wrote:
> How would I go about generating a backtrace inside my exception
> handler? e.g., say I wanted to display a nice backtrace in a web page
> when my web app is in debug mode...
there is the library stack-walker in fundev/sources/lib/stack-walker,
which
prints a stack trace.
It is not a "nice backtrace" since Dylan names are still mangled;
Also, source
record locations are not included. But most of the time it is enough
to pin down
the error location.
I don't think with the current lack of debugging information in OD (at
least on
non-win32) it is not easily possible to get a more appropriate
backtrace.
But the stack-walker could be modified to demangle Dylan names, either
using
dfmc-mangling or tools/debugger-extensions/ (incomplete C code).
Best regards,
hannes
|
