SBCL uses Launchpad to track bugs. The bug database is available at
Reporting bugs there requires registering at Launchpad. However, bugs can also be reported on the mailing list sbcl-bugs, which is moderated but does not require subscribing.
Simply send email to firstname.lastname@example.org and the bug will be checked and added to Launchpad by SBCL maintainers.
Please include enough information in a bug report that someone reading it can reproduce the problem, i.e. don't write
Subject: apparent bug in PRINT-OBJECT (or *PRINT-LENGTH*?) PRINT-OBJECT doesn't seem to work with *PRINT-LENGTH*. Is this a bug?
Subject: apparent bug in PRINT-OBJECT (or *PRINT-LENGTH*?) In sbcl-1.2.3 running under OpenBSD 4.5 on my Alpha box, when I compile and load the file (DEFSTRUCT (FOO (:PRINT-OBJECT (LAMBDA (X Y) (LET ((*PRINT-LENGTH* 4)) (PRINT X Y))))) X Y) then at the command line type (MAKE-FOO) the program loops endlessly instead of printing the object.
A more in-depth discussion on reporting bugs effectively can be found at
If you run into a signal related bug, you are getting fatal errors
signal N is [un]blocked or just hangs, and you want to
send a useful bug report then:
:sb-ldb, see base-target-features.lisp-expr) and change
#define QSHOW_SIGNAL 0to
#define QSHOW_SIGNAL 1in src/runtime/runtime.h.
kill -ABRT <pidof sbcl>.
gdb -p <pidof sbcl>and get backtraces for all threads:
thread apply all ba.
thread apply all call_backtrace_from_fp($ebp, 100). Substitute $ebp with $rbp on x86-64. The backtraces will appear in the stdout of the SBCL process.