[Dovecot] Core dump in 2.0-beta4 and latest Mercurial
I'm seeing core-dumps with both 2.0-beta4 and a fresh checkout from Mercurial. I'm very new to Dovecot, so there's a good chance this is caused by my limited experience with Dovecot configuration, but it's my understanding that any core-dump is considered a bug (nice policy by the way).
The installation seemed to be working as expected until I added the two namespaces and tried to set up shared mailboxes.
Timo: The installation is running on a KVM dedicated to testing Dovecot, so if you want to debug anything in my environment, just send me your SSH key, and I'll set it up.
Attached files (from test with latest Mercurial):
dialog.txt: IMAP dialogue to reproduce the core dump mail.info.txt: Resulting log entries debug.log.txt: Resulting debug-log entries bt-full.txt: br full for dumped core dovecot-n.txt: Output of dovecot -n sql.txt: passdb/userdb SQL configuration
-- Regards B. Johannessen
On Tue, 2010-04-06 at 01:13 +0200, B. Johannessen wrote:
#1 0x00323bcf in mailbox_list_mailbox (list=0x822c8c8, name=0x8061178 "", flags_r=0xbfd7692c) at mailbox-list.c:709 path = 0x8234f50 "/mailstore/db.org/users//Maildir" fname = <value optimized out> rootdir = 0x0
I can't really understand why rootdir=NULL, but path isn't NULL. I couldn't reproduce it in my few tests. But I guess it doesn't matter all that much, this fixes it: http://hg.dovecot.org/dovecot-2.0/rev/0e7125f1e27e
participants (2)
-
B. Johannessen
-
Timo Sirainen