On Aug 8, 2008, at 1:17 AM, John Wood wrote:
Can you still reproduce this crash? http://dovecot.org/bugreport.html lists some things about how to get a core dump.I changed things to try to get a core and, of course, for nearly a 2 weeks got nothing at all. Figures. After you released 1.1.2 I went ahead and updated. A few days later I got a nice core waiting for me.Unfortunately I made the mistake of not watching the ports build and didn't see that that it lacked -g, so the backtrace is only partially useful.
It doesn't show much more than that it most likely died in FETCH command. A lot of the function call order is impossible so the backtrace was somehow wrong/corrupted.
In an attempt to stop wasting your time I have recompiled with -g and an now running that set of binaries. The next time this happens I should have useful backtrace for 1.1.2.
Thanks.
I doubt the message itself had anything to do with it. Just deleting dovecot.index.cache probably fixes the issue? Anyway I just tried causing the "Broken MIME parts" error myself. Icouldn't get Dovecot to crash (and the problem got fixed automatically).I've not gone as far as doing that. All of the users on this system use mbox format, so if you think it would help I can just run a find | xargs to remove all of the dovecot.index.cache files. However, if I do this I may deny you the chance to see what keeps causing this. Would you prefer I leave it and try for another core? The crashes do not happen enough that users are screaming for my blood, yet :)
Just leave them for now :)
PGP.sig
Description: This is a digitally signed message part
