Hello. With dovecot ver. from 20130211 I have a segfault on doveadm when sync. There are messages from server: 2013-02-14T12:42:35.508031+04:00 imap1 kernel: [870542.927083] doveadm-server[9483]: segfault at 4 ip 00000074b228bc24 sp 000003f30b8e61b0 error 4 in doveadm-server[74b226b000+3a000] or 2013-02-14T12:47:39.850942+04:00 imap1 kernel: [870847.279513] doveadm[9513]: segfault at 4 ip 00000006b31ac294 sp 000003dc5c669a90 error 4 in doveadm[6b3178000+5f000] I cannot catch process doveadm-server by strace because it starts with unknown PID on demand.
On 2013-02-14 4:16 AM, Evgeny Basov <ya.mwork at yandex.ru> wrote:> With dovecot ver. from 20130211 I have a segfault on doveadm when sync. > There are messages from server:Since you are using hg version, shouldn't you always upgrade to latest before reporting a problem? Maybe it isn't expected, but I know I would... -- Best regards, */Charles/*
On Thu, 2013-02-14 at 13:16 +0400, Evgeny Basov wrote:> Hello. > > With dovecot ver. from 20130211 I have a segfault on doveadm when sync. > There are messages from server: > > 2013-02-14T12:42:35.508031+04:00 imap1 kernel: [870542.927083] > doveadm-server[9483]: segfault at 4 ip 00000074b228bc24 sp > 000003f30b8e61b0 error 4 in doveadm-server[74b226b000+3a000] > > I cannot catch process doveadm-server by strace because it starts with > unknown PID on demand.strace isn't useful for debugging crashes, gdb backtrace is. You should be able to get a core dump from doveadm-server (I've definitely been debugging those today many times). http://dovecot.org/bugreport.html Anyway, the crash is probably fixed by today's changes.