12:36:08francogrexhi is it possible to reconnect to a running thread: debugger invoked on a SB-INT:SIMPLE-READER-PACKAGE-ERROR in thread #<THREAD "main thread" RUNNING {23EE7E89}>
12:36:29francogrexsbcl hangs and i would like to open another sbcl and connect it to that hanging running thread
13:07:487GHAAK86Ascymtym: yes it happens with more recent versions http://pastecode.ru/294008/
13:23:537GHAAK86Ahm the backtrace is incomplete on that paste link, lemme paste again
22:06:06scymtymattila_lendvai: i was going to fix a problem in INSPECT and stumbled upon an apparent problem with *SUPPRESS-PRINT-ERRORS*. do you have a minute to discuss this?
22:09:58attila_lendvaiACTION greps around to remind himself
22:10:48scymtymi basically wanted to use *SUPPRESS-PRINT-ERRORS* in INSPECT when printing slot values since that can signal errors (e.g. in case of user-written PRINT-OBJECT methods)
22:11:25scymtymthis seemed to work initially, but failed in the context of the test harness
22:12:15scymtymthe reason is that the test harness establishes a condition handler that handles error conditions (or maybe serious conditions, i don't remember)
22:13:33scymtymthis is because the code in OUTPUT-OBJECT SIGNALs the condition to ;; Give outer handlers a chance.