BUG: clisp crashes (version 2.38_1)

[vincent-opdarw@…]

During the installation of clisp 2.38_1+darwin_8 (configure, then make), I got several crashes, but the build went on until the end and the port was installed. In particular, clisp crashes:

Date/Time: 2006-04-12 22:56:31.659 +0200 OS Version: 10.4.6 (Build 8I127) Report Version: 4

Command: lisp.run Path: /opt/local/lib/clisp/base/lisp.run Parent: zsh [14286]

Version: ??? (???)

PID: 15430 Thread: 0

Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x19faa014

Thread 0 Crashed: 0 lisp.run 0x000706ac closed_buffered + 48 (crt.c:355) 1 lisp.run 0x0007906c closed_all_files + 108 (crt.c:355) 2 lisp.run 0x00028efc loadmem_from_handle + 3356 (crt.c:355) 3 lisp.run 0x000290e4 loadmem + 132 (crt.c:355) 4 lisp.run 0x000294f0 init_memory + 900 (crt.c:355) 5 lisp.run 0x0002bb40 main + 3972 (crt.c:355) 6 lisp.run 0x00002338 _start + 340 (crt.c:272) 7 lisp.run 0x000021e0 start + 60

Thread 0 crashed with PPC Thread State 64:

srr0: 0x00000000000706ac srr1: 0x100000000000d030 vrsave: 0x0000000000000000

cr: 0x22000408 xer: 0x0000000000000000 lr: 0x000000000007906c ctr: 0x0000000000000001 r0: 0x000000000007906c r1: 0x00000000bfffe410 r2: 0x0000000000000000 r3: 0x0000000000000000 r4: 0x0000000000500490 r5: 0x00000000bfffe378 r6: 0x0000000000000000 r7: 0x0000000000070684 r8: 0x00000000001a3b09 r9: 0x0000000019faa020 r10: 0x0000000019fa9fc0 r11: 0x0000000000000000

r12: 0x000000009000660c r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000 r16: 0x000000000019b040 r17: 0x000000000019b014 r18: 0x0000000000000001 r19: 0x000000000019b014 r20: 0x00000000bfffe450 r21: 0x00000000bfffe470 r22: 0x0000000000000004 r23: 0x00000000005004c0 r24: 0x00000000001a3b09 r25: 0x00000000001b9008 r26: 0x00000000001b9008 r27: 0xfffffffffffffff6 r28: 0x000000006672dfd0 r29: 0x0000000019fa9fc1 r30: 0x0000000019fa9fc0 r31: 0x0000000000079008

Binary Images Description:

0x1000 - 0x19afff lisp.run /opt/local/lib/clisp/base/lisp.run

0x305000 - 0x30cfff libintl.3.dylib /opt/local/lib/libintl.3.dylib 0x321000 - 0x3f7fff libiconv.2.dylib /opt/local/lib/libiconv.2.dylib 0x42f000 - 0x450fff libreadline.5.0.dylib /opt/local/lib/libreadline.5.0.dylib

0x8fe00000 - 0x8fe51fff dyld 44.4 /usr/lib/dyld 0x90000000 - 0x901bbfff libSystem.B.dylib /usr/lib/libSystem.B.dylib 0x90213000 - 0x90218fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib 0x907c1000 - 0x9089afff com.apple.CoreFoundation 6.4.4 (368.25) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x908e5000 - 0x909e7fff libicucore.A.dylib /usr/lib/libicucore.A.dylib 0x90a41000 - 0x90ac5fff libobjc.A.dylib /usr/lib/libobjc.A.dylib 0x90b74000 - 0x90b86fff libauto.dylib /usr/lib/libauto.dylib 0x91436000 - 0x91441fff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib 0x91446000 - 0x91466fff libmx.A.dylib /usr/lib/libmx.A.dylib 0x965c1000 - 0x965effff libncurses.5.4.dylib /usr/lib/libncurses.5.4.dylib

Model: PowerMac7,3, BootROM 5.2.4f1, 2 processors, PowerPC G5 (3.1), 2.7 GHz, 1.5 GB Graphics: ATI Radeon 9650, ATY,RV351, AGP, 256 MB Memory Module: DIMM0/J11, 256 MB, DDR SDRAM, PC3200U-30330 Memory Module: DIMM1/J12, 256 MB, DDR SDRAM, PC3200U-30330 Memory Module: DIMM2/J13, 512 MB, DDR SDRAM, PC3200U-30330 Memory Module: DIMM3/J14, 512 MB, DDR SDRAM, PC3200U-30330 Network Service: Ethernet intégré, Ethernet, en0 PCI Card: AlchemyTV, tv-card, SLOT-3 Serial ATA Device: Maxtor 6B250S0, 233.76 GB Parallel ATA Device: PIONEER DVD-RW DVR-109, USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA USB Device: USB-PS/2 Optical Mouse, Logitech, Up to 1.5 Mb/sec, 100 mA USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA

[gwright@…]

Hi Vincent, I'll take a look at this but it may be an upstream bug. Clisp is not well tested on G5s (I don't think the developers have access to a G5 machine).

As unpleasant as it seems, you may want to check your memory as well. (Pull the memory sticks out in pairs and try running the build. Don't trust a memory test program---in my former company we had memory modules that passed memory test programs and still led to somewhat repeatable segmentation faults.

It would be particularly helpful to know if you still had crashes if you reduced your installed memory to 512 MB or 1 GB. There may be some memory model limitation in clisp.

Also, clean out everything (sudo port clean --all clisp) and run

sudo port -dv destroot > dest.log 2>&1

If you do this procedure twice (clean; then build) does it crash in the same place?

-Greg

[vincent-opdarw@…]

I haven't had the time to look at it more closely, but someone has the same problem as me:

​http://groups.google.com/group/fr.comp.os.mac-os.x/msg/af8b6cd591ec84cc

[gwright@…]

Hi Vincent,

An idea: try building using the +nolibsigsegv variant. This works around bugs in OS X in which signals get handled incorrectly by the operating system.

-Greg

[gwright@…]

Hi Vincent,

I'm marking this bug as a duplicate of 7557, as the problem seems to be the same. I have also suggested to the original poster that he try the +nolibsigsegv variant.

-Greg

* This bug has been marked as a duplicate of 7557 *