[armedbear-devel] recording source file locations
alanruttenberg at gmail.com
Wed Mar 3 13:36:49 UTC 2010
On Wed, Mar 3, 2010 at 4:48 AM, Tobias C. Rittweiler <tcr at freebits.de> wrote:
> Alan Ruttenberg writes:
> Losing in what way exactly? Getting an error message in the minibuffer,
> or getting to the wrong place?
Sometimes going to the wrong place. I can fix that. But more often not
going anywhere because source isn't recorded, or because slime doesn't
know where to find the recorded source.
>> 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!
Cool. The challenge for ABCL is getting *any* locals information. :)
> 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.
> armedbear-devel mailing list
> armedbear-devel at common-lisp.net
More information about the armedbear-devel