On dapper you can install evolution-dbg and evolution-data-server-dbg to get debug symbols for it, it would probably make the backtrace better.
" *** glibc detected *** corrupted double-linked list: 0x00000000005daa00 ***" is likely to be the issue. Getting a log with valgrind could be useful. Install the valgrind package and run "valgrind --trace-children=yes evolution", then get the issue ... it makes the program really slow but is useful to catch errors than can give a such message by example -- Dapper64 - Viewing Evolution Help Contents Kills Evolution Until Reboot https://launchpad.net/bugs/37723 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
