[armedbear-devel] recording source file locations
Tobias C. Rittweiler
tcr at freebits.de
Wed Mar 3 09:48:00 UTC 2010
Alan Ruttenberg writes:
> Can anyone summarize what kinds of source information are recorded? Is
> source location for generic function methods recorded? Variables?
> Constants? Stuctures?
> I'd like to extend source recording for functions defined
> interactively in slime as well, if I can understand what needs to be
> done on the abcl side.
> I could hunt around the source but figured I'd ask in case someone has
> thought of this recently.
> I'm losing in slime most of the time I meta-point things.
Losing in what way exactly? Getting an error message in the minibuffer,
or getting to the wrong place?
> On another debugging front, is it possible to get local variables for
> functions that are interpreted, in the context of an exception? I
> understand it's more difficult for compiled functions.
I'm changing Slime so backends can provide even more information than
just local lexical variables.
For example, see
on how the backend for the ECL implementations reports locally bound
specials, and even restarts next to local lexical variables!
I'm saying this for the brave hero who tackles this problem so he knows
that the more information he can press out of a stack frame the better.
More information about the armedbear-devel