dev-lisp/cmucl-bin-18d-r1 emerged today on a gentoo 1.4rc2, gcc-3.2.2, glibc-2.3.1-r2. the 'lisp' command just crashes with a segmentation fault on load. gdb doesn't provide much meaningful information: $ export CMUCLLIB=/opt/cmucl/lib $ gdb /opt/cmucl/bin/lisp Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... (no debugging symbols found)... (gdb) run Starting program: /opt/cmucl/bin/lisp (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x67ffffff in ?? () (gdb) where #0 0x67ffffff in ?? () Cannot access memory at address 0x0 (gdb) info registers eax 0x48000000 1207959552 ecx 0x20000000 536870912 edx 0x7 7 ebx 0x48000000 1207959552 esp 0xbffff93c 0xbffff93c ebp 0x0 0x0 esi 0x4032 16434 edi 0xffffffff -1 eip 0x67ffffff 0x67ffffff eflags 0x10246 66118 cs 0x23 35 ss 0x2b 43 ds 0x2b 43 es 0x2b 43 fs 0x0 0 gs 0x0 0 (gdb) quit Reproducible: Always Steps to Reproduce: 1. run 'lisp' at prompt Actual Results: $ lisp Segmentation fault Expected Results: lisp interpreter eval-run loop (prompt) should have been provided
Hmm.. haven't tried it with glibc-2.3.x; it works nicely with glibc-2.2.x. As it's not compiled from source (and even it if was, it'd not use gcc), that's not a problem. I'll see if I can't test it with 2.3.x soon.
Hmm. A system bootstrapped from 1.4_rc4, with glibc-2.3.1-r4 seems to work nicely. Try doing an emerge sync; emerge -up world. If the problem persists, reopen the bug.
