[Openmcl-devel] mystery SEGV starting 64bit ccl on linux

Bit Twiddler bitwiddler at gmail.com
Thu Nov 18 20:32:29 UTC 2010


I'm getting sporadic crashes starting ccl on various linuxes
(CentOS 5.5, Scientific Linux 5.5, and Open Suse 11.3)

Current directory is ~/p/cl/ccl/1.5/release/ccl/
GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-23.el5_5.1)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from
/mnt/data1/home1/dsm/p/cl/ccl/1.5/release/ccl/lx86cl64...done.
(gdb) run
Starting program: /mnt/data1/home1/xxx/p/cl/ccl/1.5/release/ccl/lx86cl64
[Thread debugging using libthread_db enabled]
Reserving heap at 0x300000000000, size 0x8000000000
Committing memory at 0x302000000000, size 0x540000
Committing memory at 0x307c00000000, size 0xb000
Committing memory at 0x307e3f800000, size 0xb000
Committing memory at 0x302000540000, size 0x2000000
Committing memory at 0x307c0000b000, size 0x40000
Unprotecting memory at 0x307c0000b000, size 0x40000
Committing memory at 0x307e3f80b000, size 0x40000
Unprotecting memory at 0x307e3f80b000, size 0x40000
Mapping stack of size 0x24d000
Protecting memory at 0x2aaaaaacb000, size 0x1000
Protecting memory at 0x2aaaaaacc000, size 0x19000
Mapping stack of size 0x51000
Protecting memory at 0x2aaaaad18000, size 0x10000

Program received signal SIGSEGV, Segmentation fault.
0x0000300000ab133f in ?? ()
(gdb) bt
#0  0x0000300000ab133f in ?? ()
#1  0x000030200052f8af in ?? ()
#2  0x00002aaaaad16ff0 in ?? ()
#3  0x00000000004122c4 in toplevel_loop () at ../x86-subprims64.s:60
Backtrace stopped: frame did not save the PC
(gdb)

I don't understand why gdb can't display the backtrace, I have
the optimizer turned off, and -g turned on.

Previously, I was able to get a crash after a mmap call to allocate
a stack segment, but now the program runs after that, and I wind
up with the above situation.

Does anybody know of any debugging code that I can enable?
I turned on DEBUG_MEMORY by setting it to 1 in memory.c
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clozure.com/pipermail/openmcl-devel/attachments/20101118/3b20cb93/attachment.html>


More information about the Openmcl-devel mailing list