[Dovecot] imap-login: memory corruption

[Ralf Hildebrandt]

>From my logs (dovecot-1.1.8)

Jan 14 08:42:52 postamt dovecot: imap-login: *** glibc detected *** imap-login: malloc(): memory corruption: 0x0844e778 ***
Jan 14 08:42:52 postamt dovecot: child 15380 (login) killed with signal 6

Jan 14 10:06:42 postamt dovecot: Panic: imap-login: file ioloop.c: line 71 (io_remove_full): assertion failed: (io->callback != NULL)
Jan 14 10:06:42 postamt dovecot: child 15389 (login) killed with signal 6

Jan 14 10:53:15 postamt dovecot: Panic: imap-login: file ioloop.c: line 71 (io_remove_full): assertion failed: (io->callback != NULL)
Jan 14 10:53:15 postamt dovecot: child 15367 (login) killed with signal 6

Jan 14 12:05:20 postamt dovecot: imap-login: *** glibc detected *** imap-login: malloc(): memory corruption: 0x0882fe40 ***
Jan 14 12:05:20 postamt dovecot: child 2263 (login) killed with signal 6

Jan 14 12:35:13 postamt dovecot: imap-login: *** glibc detected *** imap-login: free(): invalid pointer: 0x08a46620 ***
Jan 14 12:35:13 postamt dovecot: child 4169 (login) killed with signal 6

Jan 14 13:08:27 postamt dovecot: imap-login: *** glibc detected *** imap-login: free(): invalid pointer: 0x08f5b5b0 ***
Jan 14 13:08:27 postamt dovecot: child 6316 (login) killed with signal 6

Jan 14 13:18:00 postamt dovecot: imap-login: *** glibc detected *** imap-login: malloc(): memory corruption: 0x085f3d48 ***
Jan 14 13:18:00 postamt dovecot: child 15378 (login) killed with signal 6

-- 
Ralf Hildebrandt (Ralf.Hildebrandt at charite.de)          snickebo at charite.de
Postfix - Einrichtung, Betrieb und Wartung       Tel. +49 (0)30-450 570-155
http://www.arschkrebs.de
IMPORTANT - ANTI-DISCLAIMER - This email is not and cannot, by its
nature, be confidential. En route from me to you, it will pass across
the public Internet, easily readable by any number of system
administrators along the way. If you have received this message by
mistake, it would be ridiculous for me to tell you not to read it or
copy to anyone else, because, let's face it, if it's a message
revealing confidential information or that could embarrass me
intensely, that's precisely what you'll do. Who wouldn't? Likewise, it
is superfluous for me to claim copyright in the contents, because I
own that anyway, even if you print out a hard copy or disseminate this
message all over the known universe. I don't know why so many
corporate mail servers feel impelled to attach a disclaimer to the
bottom of every email message saying otherwise. If you don't know
either, why not email your corporate lawyers and system administrators
and ask them why they insist on contributing so much to the waste of
bandwidth? To say nothing of making the presence of your mail on
public discussions or mailinglists of explicitly contratictory nature.
May as well just delete it, eh? Oh, and this message is probably
plagued with viruses as well.