Re: Intermittent errors on ARM with gdc

Andrew W

Posted Thu, 17 Oct 2013 21:41:22 GMT in reply to Andrew W

and more :-

(gdb) cont
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0x001ad15c in gcaddRange () at ../../../../gcc-4.8-20131010/libphobos/libdruntime/gc/gc.d:293
#2 0x00174fb4 in vibe.utils.memory.T19FreeListObjectAllocTS4vibe4core7drivers13libevent2tcp10TCPContextVb0Vb1Z._T5allocTC4vibe4core6driver10DriverCoreTPS6deimos6event212eventstruct10eventbaseTiTPS6deimos6event211bufferevent11buffereventTS4vibe4core3net14NetworkAddressTS4vibe4core3net14NetworkAddressZ.alloc() ()
#3 0x00034008 in vibe.core.drivers.libevent2tcp.onConnect() ()
#4 0x00043430 in vibe.core.core.CoreTask.run() ()
#5 0x001a37fc in fiber_entryPoint () at ../../../../gcc-4.8-20131010/libphobos/libdruntime/core/thread.d:3800
#6 0xb6cbe0b0 in setcontext () from /lib/arm-linux-gnueabihf/libc.so.6
#7 0xb6cbe0b0 in setcontext () from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

This looks pretty horrible - a problem with GDC maybe ?