From: Harald Hanche-O. <ha...@ma...> - 2009-03-17 09:02:28
|
Oh heck, let me bypass the moderator business. Here is my email again, sans attachments: + Gábor Melis <me...@re...>: > Remove the --disable-debugger from tests/subr.sh for now. Thanks; that did the trick. So let me take it from the top: This is on macosx 10.5.6 running on ppc (12 inch powerbook g4 if you must know). git bisect tells me this: aa0ed5a420ea5295d586b3f323b5375d3b506860 is first bad commit commit aa0ed5a420ea5295d586b3f323b5375d3b506860 Author: Gabor Melis <me...@ho...> Date: Mon Feb 16 22:01:15 2009 +0000 1.0.25.37: block deferrables when gc pending in PA After determining this, I ran "git bisect reset", so I am once again at 1.0.26.1. Following instructions as best I could, I ran the test and got a backtrace. I have made stdout and stderr output available as separate files; I hope that doesn't complicate things. See here: http://www.math.ntnu.no/~hanche/tmp/sbcl-test-stdout.txt http://www.math.ntnu.no/~hanche/tmp/sbcl-test-stderr.txt Basically, where you find this text in stderr fatal error encountered in SBCL pid 8564: deferrable signal 1 blocked is where I get into ldb as seen in stdout. To my great surprise, after ldb had printed its backtrace, lisp continued executing, so I couldn't attach with gdb. If you wish me to, I can redo the process and attach with gdb while the ldb> prompt is up. However, I should mention that I haven't enabled threading, so maybe that point is moot? - Harald |