So. I believe this bug is defiantly not a duplicate of #215904. I've looked at the code and there's something that puzzles me and that's how sb_debug_write is in the stack trace 6 times like it is recursively calling itself. Is this what his happening in the macro LBER_SBIOD_WRITE_NEXT()?
** Attachment added: "Backtrace with call values and local variables." http://launchpadlibrarian.net/15645277/gdb-evolution-exchange-storage.txt9 -- evolution-exchange-storage crash in e2k_global_catalog_lookup and ber_flush2 https://bugs.launchpad.net/bugs/239184 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
