> This doesn't make much sense. Is it reproducible?
I’m not sure what triggered it exactly, was just completely random. Looking in
the logs there was nothing at the time.
If it happens again (with similar trace) will follow-up.
--
Robert
inoc.net!rblayzor
XMPP: rblayzor.AT.inoc.net
PGP Key: 78
> On 03 Mar 2016, at 18:17, Robert Blayzor wrote:
>
> pid 31943 (dovecot), uid 0: exited on signal 11 (core dumped)
>
>
> dovecot --version
> 2.2.21 (5345f22)
>
> uname -a
> FreeBSD 10.3-BETA2 #0 r295966M: amd64
>
>
> (gdb) bt full
> #0 0x0008008eb037 in t_push (marker=0x0) at data-
pid 31943 (dovecot), uid 0: exited on signal 11 (core dumped)
dovecot --version
2.2.21 (5345f22)
uname -a
FreeBSD 10.3-BETA2 #0 r295966M: amd64
bt full
#0 0x0008008eb037 in t_push (marker=0x0) at data-stack.c:133
133 data-stack.c: No such file or directory.
in data-stack.c
On Jan 31, 2016, at 4:26 AM, Timo Sirainen wrote:
>
> There's no way it can crash here, unless something's badly broken. Either a
> buggy compiler or maybe memory corruption earlier in the process. Can you
> reproduce it? Can you run it via valgrind?
I’ve been tracking this with an open bug i
On 31 Jan 2016, at 04:47, Robert Blayzor wrote:
>
>
> dovecot --version
> 2.2.21 (5345f22)
>
> FreeBSD 10.2-RELEASE-p11 FreeBSD 10.2-RELEASE-p11 #0 r294908M: amd64
>
>
> #0 0x000800910c74 in io_loop_time_refresh () at ioloop.c:635
> 635 ioloop.c: No such file or directory.
There's no
dovecot --version
2.2.21 (5345f22)
FreeBSD 10.2-RELEASE-p11 FreeBSD 10.2-RELEASE-p11 #0 r294908M: amd64
Core was generated by `dovecot'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/local/lib/dovecot/libdovecot.so.0...done.
Loaded symbols for /usr/local/lib/
