search

diiq / Tainted-Oyster

A FEXPR-based lisp, for first-class, hygenic macro magic.
10 stars 2 forks source link

Stack Trace #1

Open diiq opened 13 years ago

diiq commented 13 years ago

Right now, the stack trace given by an unhandled signal lists what would have happened, if the signal had not been, uh, signaled.

A useful stack trace would show what had occurred up to that point, instead.

Build a separate stack tracer, that can be turned on or off.

diiq commented 13 years ago

A good start has been made on this. Stack traces now show the name-or-call-that-produced for each function in the pseudo-stack up to the unhandled signal. I am debating what else needs to be shown. Arguments? The actual value of the function --- that is, the code? Scope?

Making it interactive might be necessary.

Line numbers, too. That should be a separate issue, though.

Also, stack traces should be reifyable into oyster objects, so that they can be manipulated and printed in varying ways.