On 26.6.2014, at 16.10, Urban Loesch <bind@enas.net> wrote:
#1 0x00007fbf26650c44 in mailbox_save_cancel (_ctx=<optimized out>) at mail-storage.c:2116 ctx = 0xa95500 keywords = 0x0 mail = <optimized out> #2 0x00007fbf2665104f in mailbox_save_begin (ctx=ctx@entry=0x7fff64b53048, input=0xaaaea0) at mail-storage.c:2041 box = 0xa6f800 ret = <optimized out> #3 0x00007fbf26648bb6 in mail_storage_try_copy (mail=0xa90d20, _ctx=0x7fff64b53048) at mail-copy.c:76 ctx = 0xa95500 pmail = 0xa90d20 input = 0xaaaea0 #4 mail_storage_copy (ctx=0x0, mail=0xa90d20) at mail-copy.c:101 No locals. #5 0x00007fbf24f12679 in notify_copy (ctx=0xa95500, mail=0xa90d20) at notify-storage.c:107 lt = 0xa8bdd0 lbox = 0xa70870 ret = <optimized out> #6 0x00007fbf2573d06b in acl_copy (ctx=0xa95500, mail=0xa90d20) at acl-mailbox.c:435 t = <optimized out> abox = 0xa6fe48 #7 0x00007fbf26650e8d in mailbox_copy (_ctx=_ctx@entry=0x7fff64b53190, mail=0xa90d20) at mail-storage.c:2152 ctx = 0xa95500 t = 0xa8de20 keywords = 0x0 pvt_flags = 0 backend_mail = 0xa90d20 ret = <optimized out> __FUNCTION__ = "mailbox_copy"
The client is trying to use COPY or MOVE command, but the copying fails for some reason and the cleanup code crashes. I can't reproduce this though, so would be helpful to know what exactly it's doing. So getting the gdb output for these commands (instead of just bt full) would help:
p *ctx p *ctx.dest_mail f 7 p (*_ctx).transaction.box.vname p (*_ctx).transaction.box.storage.error_string p mail.box.vname