freenode/#clasp - IRC Chatlog
Search
13:32:23
drmeister
And we have to create them without allocating any objects because I want to use them to load the snapshot - that brings all the objects into memory.
13:35:41
drmeister
Or I need to look carefully at what I'm doing in the ClaspPlugin like here https://github.com/clasp-developers/clasp/blob/main/src/llvmo/llvmoExpose.cc#L4299
0:52:58
drmeister
Hey Bike - I'm working with cando and slime and jumping to source code is giving interpretable but unexpected errors.
1:05:26
drmeister
Pulling a new slime doesn't fix the problem - the swank/clasp.lisp assumes the (clasp-debug:frame-source-location (frame-from-number frame-number))) returns a code-source-line object.
1:05:51
drmeister
It's really nice that when I M-. on (code-debug:code-source-line-pathname it jumps here though...
1:05:56
drmeister
https://github.com/clasp-developers/clasp/blob/main/src/lisp/kernel/lsp/debug.lsp#L48
1:06:31
drmeister
What happens is that (clasp-debug:frame-source-location (frame-from-number frame-number))) actually returns a #<source-pos-info ...> object.
1:24:57
Bike
frame-source-location should always return a code-source-line or nil, so returning a source pos info is wrong
1:26:45
Bike
mhm, the DebuggerFrame_O has a spi in it, which should be converted into a code-source-line by clasp-debug but isn't
1:27:49
Bike
alternately we could finally decide on a single source position object to use. we have like four at this point? but that would be more involved
1:28:40
Bike
also there's unfortunately no source info for C++ at all. all C++ frames have is the function name