Stack trace on debugging

[ecraven]

When I run (+ 1 'a) on a repl, I see the following stack frames:

> (+ 1 'a)
Exception in +: a is not a number
Type (debug) to enter the debugger.
> (debug)
debug> ?
Type i  to inspect the raise continuation (if available)
     s  to display the condition
     c  to inspect the condition
     e  or eof to exit the debugger, retaining error continuation
     q  to exit the debugger, discarding error continuation
debug> i
#<system continuation in winder-dummy>                            : sf
  0: #<system continuation in winder-dummy>
  1: #<system continuation in new-cafe>

Is there any way to see actual information on (+ 1 'a) i.e. the form that actually raised the condition? For more complex programs with multi-level libraries, it can be very hard to discern where the actual error occurred (especially since chez is such a good compiler ;) Also, is there a way to extract the source location from a continuation programmatically from the object returned from inspect/object (filename, line, and column)?

[jltaylor-us]

See #128

[tisonkun]

FWIW http://cisco.github.io/ChezScheme/csug9.5/debug.html#./debug:h0

[amirouche]

Is it a bug?

[akeep]

I do not believe so, that is the full error trace for that expression.