freenode/#sbcl - IRC Chatlog
Search
10:58:39
scymtym
for the "visit source of unprintable frame" method, better untrace everything first so print errors don't get in the way
11:04:43
flip214
I *believe* that ~/src/sbcl/src/code/print.lisp output-object print-it, the (funcall fun stream object) call is the bad call
11:05:37
flip214
but why would pprint-dispatch return sb-impl::%print-unreadable-object? that's incompatible, too
13:23:22
stassats
flip214: just hold on, the fact that you had ask here means we're doing something wrong
13:24:02
stassats
ok, [error printing frame], is the whole frame unprintable? i bet the function name is printable
13:29:45
flip214
stassats: I'm sorry if I seem to blame someone around here. That's not my intention!
13:31:56
stassats
i meant sbcl should present the errors in a way that doesn't require #sbcl to decipher
13:34:09
flip214
reminded me of "The night watch" ( I HAVE NO TOOLS BECAUSE I'VE DESTROYED MY TOOLS WITH MY TOOLS.
13:35:33
flip214
stassats: well, slime does (setf (fdefinition 'sb-impl::%print-unreadable-object) ...)
13:36:10
flip214
if something in there is broken (or gets broken _at_that_level_), SBCL won't be able to help any more.
13:36:28
flip214
anything you can do to make that easier to debug next time would be very welcome, of course!
13:42:34
flip214
stassats: that is much better, would you append issue 213 or tell me what to note there?
14:09:58
pfdietz
20M test cases through the random tester, no failures. stack analyze seems to be working.
14:16:25
flip214
minion: memo for stassats: how about doing https://sourceforge.net/p/sbcl/mailman/message/33102884/ so that the interface becomes defined?
15:02:41
minion
stassats, memo from flip214: how about doing https://sourceforge.net/p/sbcl/mailman/message/33102884/ so that the interface becomes defined?