7:16:02NilbyIt's in a debugger running on sbcl. Happens when I'm examining the stack.
7:18:44NilbyIt's very difficult when there's simultaneously a bug in my program, the debugger, and errors in implementation print-object methods.
7:19:09beachI agree. Buggy tools make things very difficult.
8:39:36NilbyI wonder what it means when #<FUNCTION <<error printing object>> shows up sbcl's slime backtrace
8:40:56hayleyIt means the object couldn't be printed for some reason, so you get that text to have any backtrace at all.
8:41:20beachIt looks like someone defined a method on PRINT-OBJECT that calls PRINT-UNREADABLE-OBJECT, but that method is buggy.
8:43:06NilbyShould I be concerned? Why wouldn't I be able to print something?
8:43:50beachIf an error is signaled during printing, then the printing fails.
9:00:21ogamitaNilby: you should be concerned because it's an impediment of your debugging capabilities. You should identify the buggy print-object method and debug it.