freenode/#clasp - IRC Chatlog
Search
15:55:33
beach
I can't figure out whether the ones your wife made were the best, or the ones you had in Malaga were the best.
15:56:40
drmeister
The ones I had in Malaga tasted wonderful. The ones my wife made were made with love.
17:25:59
beach
kpoeck: Thanks for the report. I think that's Bike's code, so he can check it for you.
18:12:26
kpoeck
without latest sources and no local changes, even with distclean, the build stops in bclasp loading src/lisp/kernel/clos/fixup.lsp
18:13:03
kpoeck
lldb says thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=EXC_I386_GPFLT) frame #0: 0x000000010df909dc iclasp-boehm`(anonymous namespace)::FoldBitCast(llvm::Constant*, llvm::Type*, llvm::DataLayout const&) + 169
19:31:42
drmeister
I've been adding a bulletproof lisp backtrace function - it would help me here if it really were bulletproof.
20:07:26
frgo
I've been adding a #1="bulletproof" lisp backtrace function - it would help me here if it really were #1#. Reader Error.
20:27:26
Bike
the only change i made to the fastgf code which actually runs is eliminating an unused "cur-arg" argument in generate-outcome and below
20:28:50
Bike
https://github.com/clasp-developers/clasp/commit/2d6a567eaa9da3b4d49b316b97ddaf748c8a4be1 just scroll down to codegen-slot-reader
20:29:22
drmeister
Ok - what about moving the fastgf.cc functions around - could that have done this?
21:03:32
drmeister
kpoeck_: I'm using this as an opportunity to debug my dbg_safe_backtrace code. Bear with me for a bit while I sort this out.
21:04:39
drmeister
I'm writing a backtrace generator that displays all function names and arguments but that doesn't use the lisp printer at all because it is very often compromised when I'm in a error state like this.
21:10:33
drmeister
It knows how to introspect into objects like symbols and strings without invoking any lisp code.
21:28:33
Shinmera
kpoeck_: Were there any other changes you had to make to projects other than Definitions?
21:39:41
Shinmera
If CST is suddenly returning structs where it shouldn't, then Clasp is handling the library wrong
21:44:50
Shinmera
It must be overriding or adding a method without specialising an anything implementation defined
21:47:18
Shinmera
If we had package locks and placed one on the eclector packages we could easily catch what it does wrong
21:47:39
Bike
https://github.com/clasp-developers/clasp/blob/master/src/lisp/kernel/cleavir/translate.lisp#L669-L672