Re: [Dovecot] dovecot 1.1.4 maildir imap segfault in message_parse_header_next

2008-10-16 Thread Timo Sirainen
On Thu, 2008-10-16 at 12:07 +0200, Diego Liziero wrote: > On Thu, Oct 16, 2008 at 11:39 AM, Timo Sirainen <[EMAIL PROTECTED]> wrote: > > On Oct 16, 2008, at 11:33 AM, Diego Liziero wrote: > > > >> Today a user got this imap segfault with vanilla 1.1.4 (I don't know > > > > Hmm. And Maildir as topic

Re: [Dovecot] dovecot 1.1.4 maildir imap segfault in message_parse_header_next

2008-10-16 Thread Diego Liziero
On Thu, Oct 16, 2008 at 11:39 AM, Timo Sirainen <[EMAIL PROTECTED]> wrote: > On Oct 16, 2008, at 11:33 AM, Diego Liziero wrote: > >> Today a user got this imap segfault with vanilla 1.1.4 (I don't know > > Hmm. And Maildir as topic says? No, sorry, wrong subject, mbox >> #0 0x080c8d41 in message

Re: [Dovecot] dovecot 1.1.4 maildir imap segfault in message_parse_header_next

2008-10-16 Thread Timo Sirainen
On Oct 16, 2008, at 11:33 AM, Diego Liziero wrote: Today a user got this imap segfault with vanilla 1.1.4 (I don't know Hmm. And Maildir as topic says? #0 0x080c8d41 in message_parse_header_next (ctx=0x8774fa0, hdr_r=0xbfa438e0) at message-header-parser.c:114 p *ctx.input p *ctx.input.rea

[Dovecot] dovecot 1.1.4 maildir imap segfault in message_parse_header_next

2008-10-16 Thread Diego Liziero
I've tried to stress test dovecot 1.1.4 with imaptest for days without any assertion failure or crash. Just some "got too little data" messages. So far it's the most stable 1.1.x version. Today a user got this imap segfault with vanilla 1.1.4 (I don't know if it's something you have already fixed