On Wed, 2010-09-22 at 15:34 +0200, Burckhard Schmidt wrote:
Error: Raw backtrace: follows.
This could have been useful in pointing out where it's being called. A
imap(userx): Error: Raw backtrace: 0xff1574a8 -> 0xff1560e8 -> 0xff294fa4 -> 0xff23843c -> 0xfeca53bc -> 0xfeca5594 -> 0xfeca3ee4 -> 0xfecaf7a0 -> 0xfecb0450 -> 0xfecb06a4 -> 0xff2394e8 -> 0x1b644 -> 0x1ccb8 -> 0x1d638 -> 0x1d788 -> 0x23d60 -> 0x24070 -> 0x24204 -> 0x242a8 -> 0x244ac -> 0xff16d3c4 -> 0xff16bffc -> 0xff14b2e0 -> 0x343e0 -> 0x15b30
Nope, not useful at all. In Linux it's more useful. :) gdb backtrace would be nice though. I guess you could get it easily without core with:
gdb .../dovecot/imap <pid of imap process> cont <make it crash> bt full
This has been converted by dsync to maildir with following results: The folder "tmp" has been converted by dsync to "mail_tmp" and it lies directly under ~user/maildir containing cur/new/tmp as usual.
But the file "subscriptions" generated by dsync contains still mail/tmp.
I guess that's a bug..
- At this point dovecot crashes when the user accesses to his mailbox. We tried imap list/lsub commands too. There was a difference if we used 1 lsub "mail" "%/%" it crashes, 1 lsub "mail/" "%/%" it does not.
I can't reproduce this. What about with:
1 lsub "" %/%