Does anybody know if this is now fixed ? :-
https://bitbucket.org/goshawk/gdc/issue/120/fsection-anchors-broken-on-arm
I might be wrong but I could be facing this bug when trying to
run any of the vibe.d samples, here's an example :-
(gdb) cont
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0x001ad15c in gc_addRange () at
../../../../gcc-4.8-20131010/libphobos/libdruntime/gc/gc.d:293
#2 0x00174fb4 in
vibe.utils.memory.T19FreeListObjectAllocTS4vibe4core7drivers13libevent2_tcp10TCPContextVb0Vb1Z.T5allocTC4vibe4core6driver10DriverCoreTPS6deimos6event212eventstruct10eventbaseTiTPS6deimos6event211bufferevent11buffereventTS4vibe4core3net14NetworkAddressTS4vibe4core3net14NetworkAddressZ.alloc()
()
#3 0x00034008 in vibe.core.drivers.libevent2_tcp.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?)
