freenode/#clasp - IRC Chatlog
Search
4:23:52
drmeister
This is really starting to annoy me: ;;; Warning: compiled-function-file expected a function as argument - but it got NIL - there may not be any backtrace available
4:24:46
drmeister
Ok. The warning that is annoying me can be fixed now that we have call-with-backtrace
4:25:45
Bike
oh, i see. i forgot the no-applicable-methods case because we don't memoize it. i can fix that easily.
4:26:53
drmeister
So - clasp can dispatch on specialized types like core:simple-vector-double but the Common Lisp standard only allows specializing on 'vector - is that a problem?
6:04:41
drmeister
Now we have nice, clean backtraces. Coming soon to the docker image - (like 1.5 hours).
12:57:07
Shinmera
drmeister: the screenshot you posted had over 1000 unread emails in your gmail tab
13:07:24
drmeister
It's really not bad debugging inside of a docker container if you start it properly and install emacs and gdb.
13:08:01
drmeister
Starting it properly means: docker run --privileged --security-opt seccomp=unconfined -it -p 8888:8888 -p 4005:4005 -v $HOME:/home/app/home cracauer/cando
13:15:43
drmeister
slyrus1: Yes - but I skip over the C++ frames for now - also C++ frames don't come with arguments just yet. I'm not using the DWARF variable information and DWARF variable information is pretty messed up for any useful (non -O0) level of optimization.
13:17:01
drmeister
I'm adding the ability to use leap syntax as well as Common Lisp - that is building right now.
13:57:49
drmeister
stassats: You mentioned a way you override *stack-top-hint* in sbcl - what's up with that?
13:58:35
drmeister
ACTION just having added a *stack-top-hint* to clasp immediately wants to learn how, why and when sbcl overrides theirs.
13:59:26
drmeister
So, is it another special variable? Or do you setf sb-debug:*stack-top-hint* to nil to override it?