I'm currently working on parts of a large project that I don't have
complete control of. I don't even know all parts of it good enough
yet. What I /do/ know, though, is that I sometimes (pretty often,
actually) get completely useless backtraces where the "interesting"
function calls are replaced with calls to functions named NIL. I've
attached a part of such a backtrace below (some names modified because
the code is confidential). The frames I'm interested in in this case
are #13 and #14 - note that they both start with NIL as well as the
one in frame #16.
When the functions appearing in frames 13 to 16 where compiled (with
ASDF), SB-C::*POLICY* looked like this
((SB-EXT:INHIBIT-WARNINGS . 1)
(SPEED . 1)
(SAFETY . 3)
(COMPILATION-SPEED . 1)
(SPACE . 1)
(DEBUG . 3))
which I think is not a very aggressive setting. So, what could be the
reason for this behaviour? Any other settings that might affect this?
I skimmed the list archives a bit, but I didn't really know what to
I suppose/hope it is not expected that I see these "NIL frames" and
that I can make them go away somehow.
Thanks in advance for your help,
9: ("foreign function: call_into_lisp")
10: ("foreign function: funcall2")
11: ("foreign function: interrupt_internal_error")
12: ("foreign function: sigtrap_handler")
13: (NIL :PARTS)
16: (NIL FROB-TEST)