[Dovecot] file ostream-file.c: assertion failed with v1.0-test38
Hello,
I've some troubles logging in after upgrading to -test38. The error in the logs says:
Sep 4 02:34:38 hostname dovecot: imap-login: Login: username [123.123.123.123] Sep 4 02:34:48 hostname dovecot: IMAP(username): file ostream-file.c: line 105 (update_buffer): assertion failed: (size <= used) Sep 4 02:34:48 hostname dovecot: child 28966 (imap) returned error 1
Regards,
wouter
On 4.9.2004, at 03:43, Wouter Van Hemel wrote:
Sep 4 02:34:38 hostname dovecot: imap-login: Login: username [123.123.123.123] Sep 4 02:34:48 hostname dovecot: IMAP(username): file ostream-file.c: line 105 (update_buffer): assertion failed: (size <= used)
I can't really figure out how this could happen.. Could you get gdb backtrace? See http://dovecot.org/bugreport.html
On 4.9.2004, at 12:11, Timo Sirainen wrote:
On 4.9.2004, at 03:43, Wouter Van Hemel wrote:
Sep 4 02:34:38 hostname dovecot: imap-login: Login: username [123.123.123.123] Sep 4 02:34:48 hostname dovecot: IMAP(username): file ostream-file.c: line 105 (update_buffer): assertion failed: (size <= used)
I can't really figure out how this could happen.. Could you get gdb backtrace? See http://dovecot.org/bugreport.html
Oops, sorry, I can. It was fixed shortly afterwards, but I didn't notice more than one commit about it in ChangeLog so I thought it was already fixed in test38. Looks like my ChangeLog generator hasn't been updating it for a few days..
On Sat, 4 Sep 2004, Timo Sirainen wrote:
On 4.9.2004, at 12:11, Timo Sirainen wrote:
On 4.9.2004, at 03:43, Wouter Van Hemel wrote:
Sep 4 02:34:38 hostname dovecot: imap-login: Login: username [123.123.123.123] Sep 4 02:34:48 hostname dovecot: IMAP(username): file ostream-file.c: line 105 (update_buffer): assertion failed: (size <= used)
I can't really figure out how this could happen.. Could you get gdb backtrace? See http://dovecot.org/bugreport.html
Oops, sorry, I can. It was fixed shortly afterwards, but I didn't notice more than one commit about it in ChangeLog so I thought it was already fixed in test38. Looks like my ChangeLog generator hasn't been updating it for a few days..
... and -test39 fixes it indeed. It's been up for a few hours so far, and I haven't been able to crash it yet.
Thanks,
wouter
participants (2)
-
Timo Sirainen
-
Wouter Van Hemel