Matt Revelle <mrevelle@...> writes:
> (gdb) run
> Starting program: /opt/local/bin/sbcl
> [Thread debugging using libthread_db enabled]
> [New Thread -1210550608 (LWP 4299)]
> Program received signal SIGUSR1, User defined signal 1.
This is not a segfault: to get as far as a segfault, you need to tell
gdb to pass the SIGUSR1 (which is sent as part of sbcl's
initialization) to the underlying process and continue.
(Other benign signals, including SIGSEGV, may occur during
initialization if you have configuration files loaded, as those may
cause the write barrier to be triggered. Debugging SBCL is a little
bit of a black art.)