On Wed, 2007-12-05 at 22:02 +0200, Timo Sirainen wrote: > The glibc free() error then is a pretty serious problem. It just should > never happen no matter what you do. The backtrace shows that it's > happening on commit path when changing message flags. There's no way > there's a bug in there, so either the heap was corrupted earlier by > another code path, or there's something wrong with the server's memory. > > If it's heap corruption it's probably in some rarely run error handling > path, in which case it would help to see what errors were logged by the > same process before that.
And even better would be if you could get "bt full" gdb backtraces from them. The core files should get written to users' home directories, see http://dovecot.org/bugreport.html
signature.asc
Description: This is a digitally signed message part
