@mark: the upstream bug does not seem to be (directly) related to evo-mapi. This is the offending piece of the BT:
#0 0xb630e9f6 in *__GI_raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0xb63102f8 in *__GI_abort () at abort.c:88
#2 0xb6350873 in malloc_printerr (action=2, str=0xb640a2e5 "corrupted double-linked list", ptr=0x84afa90) at malloc.c:5999
^^^^^^^^^^^
So LIBC went on and gave out a SIGABRT. It seems an Evo upgrade was being performed/tried when this happened...
@mark: the upstream bug does not seem to be (directly) related to evo-mapi. This is the offending piece of the BT:
#0 0xb630e9f6 in *__GI_raise (sig=6) at sysdeps/ unix/sysv/ linux/raise. c:64
../nptl/
#1 0xb63102f8 in *__GI_abort () at abort.c:88
#2 0xb6350873 in malloc_printerr (action=2, str=0xb640a2e5 "corrupted double-linked list", ptr=0x84afa90) at malloc.c:5999
^^^^^^^^^^^
So LIBC went on and gave out a SIGABRT. It seems an Evo upgrade was being performed/tried when this happened...