[M3devel] Has anyone seen this crash before?

Mika Nystrom mika at async.caltech.edu
Tue Mar 1 02:49:49 CET 2011


shownew crashing on LINUXLIBC6 (works fine on e.g., AMD64_LINUX):

This GDB was configured as "i386-redhat-linux-gnu"...
(gdb) run
Starting program: /home/user/mnystrom/cm3/bin/shownew 
[Thread debugging using libthread_db enabled]
[New Thread 0xb7fb16c0 (LWP 30122)]

Program received signal SIGSEGV, Segmentation fault.
0x00be406c in ?? () from /usr/lib/libXcursor.so.1
(gdb) where
#0  0x00be406c in ?? () from /usr/lib/libXcursor.so.1
#1  0x00be44ae in ?? () from /usr/lib/libXcursor.so.1
#2  0x00be45de in XcursorLibraryLoadImages () from /usr/lib/libXcursor.so.1
#3  0x00be462b in XcursorShapeLoadImages () from /usr/lib/libXcursor.so.1
#4  0x00be4f63 in XcursorTryShapeCursor () from /usr/lib/libXcursor.so.1
#5  0x00442d02 in XCreateGlyphCursor () from /usr/lib/libX11.so.6
#6  0x0044318d in XCreateFontCursor () from /usr/lib/libX11.so.6
#7  0x00eb5a8c in XScrnCrsr__CursorLookup (orc=0xb7db6f14, name=0xf50ee4)
    at ../src/xvbt/XScrnCrsr.m3:166
#8  0x00ee491d in Cursor__NameApply (cl=0xb7db4da4, st=0xb7db6ae4)
    at ../src/vbt/Cursor.m3:104
#9  0x00ed44d1 in VBTRep__CursorApply (st=0xb7db6ae4, cl=0xb7db4da4, 
    cs={<No data fields>}) at ../src/vbt/VBTRep.m3:82
#10 0x00ee2b5c in Palette__ResolveCursor (st=0xb7db6ae4, 
    curs={<No data fields>}) at ../src/vbt/Palette.m3:294
#11 0x00ed6738 in VBTRep__CursorResolver (self=0xb7dd1aac)
    at ../src/vbt/VBTRep.m3:488
#12 0x00f9d9ed in ThreadPosix__RunThread ()
    at ../src/thread/POSIX/ThreadPosix.m3:1107
#13 0x0097aa1b in makecontext () from /lib/libc.so.6
#14 0x00000000 in ?? ()
(gdb) 

     Mika



More information about the M3devel mailing list