-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
inspect-in-frame using wrong package? #58
Comments
Strange, it works for me, but it may be lisp implementation dependent. I tried with sbcl and evaluated the form |
SBCL 1.3.14 on Debian amd64. And when I got asked about the expression to evaluate I didn't use
to be safe against all and every transformations that might happen (including macros etc.) |
How the swank debugger handles local variables depends on the lisp implementation and the optimize settings. In sbcl normally you see variables referenced as
|
Yeah, I've got that in my |
And does it work that way? If not, did you try to add this line directly to your source code? Even if it does not work with sbcl, I think it's more a swank/lisp implementation issue, slimv cannot possibly do much when the swank server hides variables/variable names. |
Well, I tested right now.
followed by the normal swank debugger window saying
This is |
Did you recompile your lisp code after adding the optimize option? Did you try to evaluate in the proper frame? I did the below and it worked for me, using sbcl 1.3.1 and swank 2.19 (the one embedded in slimv).
I loaded it into vim, connected the swank server, then compiled and loaded the source test.lisp (by pressing |
After updating to
So something's amiss. Sorry for the noise... |
When in the debugger, I can inspect local variables of functions from the backtrace.
But it should also be possible to inspect arbitrary forms using these variables; eg., with the cursor on a local variable
DATA
, I should be able to runSlimvInspect
for an expression like(1+ DATA)
.Thank you very much for the progress here... SLIMV is getting more and more awesome!
The text was updated successfully, but these errors were encountered: