libera/#clasp - IRC Chatlog
Search
15:13:37
drmeister
::notify Bike It looks like the lambda "PROGV-LAMBDA^CORE^FN^^.3" is being generated inside "FORMAT-SYMBOL^ALEXANDRIA.0.DEV^FN^^" and a DILocalVariable for a lambda variable has a !dbg entry that still has the scope for the FORMAT-SYMBOL function.
16:21:49
drmeister
::notify Bike You can reproduce the problem in clasp with (ql:quickload :alexandria) - it's friendly - you can do it repeatedly in slime.
16:41:50
drmeister
::notify Bike If on the other hand you don't load quicklisp and you just go (ql:quickload :alexandria) it will segfault because it can't read an argument in the backtrace - this is a classic example of the bug that has been plaguing us for a while wrt bad backtraces. libunwind didn't make it go away (sigh) Let's dig into it deeper.
17:41:27
drmeister
::notify Bike I put this in an issue https://github.com/clasp-developers/clasp/issues/1171
18:40:10
Colleen
Bike: drmeister said 13 hours, 42 minutes ago: There's an issue with the new dbg info. https://gist.github.com/drmeister/3a61c63587b02f45b0ecd79646b375d7
18:40:10
Colleen
Bike: drmeister said 5 hours, 26 minutes ago: That happens when compiling alexandria
18:40:10
Colleen
Bike: drmeister said 3 hours, 26 minutes ago: It looks like the lambda "PROGV-LAMBDA^CORE^FN^^.3" is being generated inside "FORMAT-SYMBOL^ALEXANDRIA.0.DEV^FN^^" and a DILocalVariable for a lambda variable has a !dbg entry that still has the scope for the FORMAT-SYMBOL function.
18:40:10
Colleen
Bike: drmeister said 2 hours, 18 minutes ago: You can reproduce the problem in clasp with (ql:quickload :alexandria) - it's friendly - you can do it repeatedly in slime.
18:40:10
Colleen
Bike: drmeister said 1 hour, 58 minutes ago: If on the other hand you don't load quicklisp and you just go (ql:quickload :alexandria) it will segfault because it can't read an argument in the backtrace - this is a classic example of the bug that has been plaguing us for a while wrt bad backtraces. libunwind didn't make it go away (sigh) Let's dig into it deeper.
18:40:10
Colleen
Bike: drmeister said 58 minutes, 43 seconds ago: I put this in an issue https://github.com/clasp-developers/clasp/issues/1171
18:40:29
Bike
i thought libunwind might not fix that, since we're still just getting RBP, and if RBP is not actually being used as the frame base register we're hosed
18:40:45
Bike
as for the new dbg info, i don't know, i guess the whole system is just really deeply broken
18:42:53
Bike
i would like to just abandon doing it in bclasp since i suspect that's a lost cause, but there's a lot of code sharing, and we still use the bclasp compiler for some stuff
18:52:33
drmeister
::notify Bike Here's another one... https://github.com/clasp-developers/clasp/issues/1172
19:13:51
drmeister
I don't think it's really deeply broken - I think we just aren't getting the right information into the dynamic variable that defines the scope. A lambda is generated that has is getting the scope of the outer function.