Hello, Let me first thank you for the bugreport, it is pretty clean and complete. On Monday 23 October 2006 01:51, J.P. Larocque wrote:
The stack trace produced below probably doesn't convey any meaningful information.
gdb does not work well with lispy environments I fear.
Loaded symbols for /lib/ld-linux.so.2 #0 0x000189f8 in handle_control_stack_guard_triggered () (gdb) bt #0 0x000189f8 in handle_control_stack_guard_triggered () #1 0x0001da80 in os_install_interrupt_handlers () #2 0x0001da80 in os_install_interrupt_handlers () Previous frame identical to this frame (corrupt stack?)
This means that it is getting a segmentation fault and thinks that it hit a 'guard page'. That page is placed just before you would overrun the control stack and if something writes to it you get a sigsegv. The handle_control_stack_guard_triggered function should then print a warning and offer the posibility to continue. It seems unlikely that the sigsegv comes from the control stack. I fear that it just gets the sigsegv because it is trying to use a memory region it cannot use.
Program received signal SIGSEGV, Segmentation fault. 0x0001516c in alloc_base_string () (gdb) bt #0 0x0001516c in alloc_base_string () #1 0x0001abb8 in main ()
This looks like a 'normal' sigsegv (we also use it to control memory allocation).
Please let me know if I can be of any help.
could you send me the output of cat /proc/self/maps and strace /usr/bin/sbcl --core /usr/lib/sbcl/sbcl-dist.core --sysinit /dev/null --userinit /dev/null Groetjes, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson|