sbcl-devel

Hi,
Is there a way to get more useful debug/bugreport information from sbcl
(look at the bottom). I have cut away some of the "unuseful" information.
------
uname -a
SunOS lispserver.mydomain.com 5.8 Generic_117350-29 sun4u sparc
-----
G E N E R A L I N F O R M A T I O N
<cut>
Manufacturer is Sun (Sun Microsystems)
Manufacturer (Short) is Sun
Manufacturer (Full) is Sun Microsystems
System Model is Ultra 2 Model 2300
Main Memory is 1.0 GB
Virtual Memory is 1.7 GB
ROM Version is OBP 3.25.0 1999/12/03 11:35
Number of CPUs (Physical) is 2
Number of CPUs (Virtual) is 2
CPU Type is UltraSPARC-II
CPU Speed is 295 MHz
App Architecture is sparc
Kernel Architecture is sun4u
Kernel Bit Size is 32
OS Name is SunOS
OS Version is 5.8
OS Distribution is Solaris 8 s28_38shwp2 SPARC
OS Distribution Name is Solaris
OS Distribution Short Name is Solaris
OS Distribution Version is 8
Libc Name is libc
Libc Version is 1
Kernel Version is SunOS Release 5.8 Version Generic_117350-29
<cut>
H A R D W A R E I N F O R M A T I O N
SUNW,Ultra-2 is a "Sun 501-3132"
<cut>
------------------------
This is SBCL 0.9.11, an implementation of ANSI Common Lisp.
<cut>
debugger invoked on a SIMPLE-ERROR: segmentation violation at #XFF3A475C
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
(no restarts: If you didn't do this on purpose, please report it as a bug.)
((FLET #:G178))
0]

Knut Olav B=F8hmer wrote:
> Is there a way to get more useful debug/bugreport information from sbcl=
> (look at the bottom). I have cut away some of the "unuseful" informati=
on.
Directions to reproduce (ie. the source that produces the error) would=20
be good to have.
You can ask SBCL for backtrace by typing "ba" and pressing enter at the
debugger prompt. That's definitely useful as well.
Cheers,
-- Nikodemus