Re: lmtp segfault after upgrade

2017-05-19 Thread Tom Sommer
On 2017-05-19 08:41, Timo Sirainen wrote: On 2 May 2017, at 11.19, Timo Sirainen wrote: On 2 May 2017, at 10.41, Tom Sommer wrote: (gdb) bt full #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 _stream = #1 0x7fe98391ff32 in

Re: lmtp segfault after upgrade

2017-05-19 Thread Timo Sirainen
On 2 May 2017, at 11.19, Timo Sirainen wrote: > > On 2 May 2017, at 10.41, Tom Sommer wrote: >> >> (gdb) bt full >> #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 >> _stream = >> #1 0x7fe98391ff32 in i_stream_concat_read_next

Re: lmtp segfault after upgrade

2017-05-18 Thread Teemu Huovila
On 18.05.2017 11:56, Tom Sommer wrote: > > > --- > Tom > > On 2017-05-18 10:05, Teemu Huovila wrote: >> On 18.05.2017 10:55, Tom Sommer wrote: >>> On 2017-05-18 09:36, Teemu Huovila wrote: Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: > On 2 May 2017, at 10.41, Tom

Re: lmtp segfault after upgrade

2017-05-18 Thread Tom Sommer
--- Tom On 2017-05-18 10:05, Teemu Huovila wrote: On 18.05.2017 10:55, Tom Sommer wrote: On 2017-05-18 09:36, Teemu Huovila wrote: Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: On 2 May 2017, at 10.41, Tom Sommer wrote: (gdb) bt full #0 i_stream_seek

Re: lmtp segfault after upgrade

2017-05-18 Thread Tom Sommer
On 2017-05-18 09:36, Teemu Huovila wrote: Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: On 2 May 2017, at 10.41, Tom Sommer wrote: (gdb) bt full #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 _stream = #1 0x7fe98391ff32 in

Re: lmtp segfault after upgrade

2017-05-18 Thread Teemu Huovila
On 18.05.2017 10:55, Tom Sommer wrote: > On 2017-05-18 09:36, Teemu Huovila wrote: >> Hello Tom >> >> On 02.05.2017 11:19, Timo Sirainen wrote: >>> On 2 May 2017, at 10.41, Tom Sommer wrote: (gdb) bt full #0 i_stream_seek (stream=0x21, v_offset=0) at

Re: lmtp segfault after upgrade

2017-05-18 Thread Tom Sommer
On 2017-05-18 09:36, Teemu Huovila wrote: Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: On 2 May 2017, at 10.41, Tom Sommer wrote: (gdb) bt full #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 _stream = #1 0x7fe98391ff32 in

Re: lmtp segfault after upgrade

2017-05-18 Thread Teemu Huovila
Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: > On 2 May 2017, at 10.41, Tom Sommer wrote: >> >> (gdb) bt full >> #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 >>_stream = >> #1 0x7fe98391ff32 in i_stream_concat_read_next (stream=0x1efe6c0)

Re: lmtp segfault after upgrade

2017-05-02 Thread Timo Sirainen
On 2 May 2017, at 10.41, Tom Sommer wrote: > > (gdb) bt full > #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 >_stream = > #1 0x7fe98391ff32 in i_stream_concat_read_next (stream=0x1efe6c0) at > istream-concat.c:77 >prev_input = 0x1ef1560 >

Re: lmtp segfault after upgrade

2017-05-02 Thread Aki Tuomi
On 2017-05-02 10:41, Tom Sommer wrote: On 2017-05-02 09:35, Aki Tuomi wrote: On 2017-05-02 10:20, Tom Sommer wrote: On 2017-05-01 19:26, Aki Tuomi wrote: On May 1, 2017 at 8:21 PM Tom Sommer wrote: I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg

Re: lmtp segfault after upgrade

2017-05-02 Thread Tom Sommer
On 2017-05-02 09:35, Aki Tuomi wrote: On 2017-05-02 10:20, Tom Sommer wrote: On 2017-05-01 19:26, Aki Tuomi wrote: On May 1, 2017 at 8:21 PM Tom Sommer wrote: I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg and /var/log/messages are getting

Re: lmtp segfault after upgrade

2017-05-02 Thread Aki Tuomi
On 2017-05-02 10:20, Tom Sommer wrote: On 2017-05-01 19:26, Aki Tuomi wrote: On May 1, 2017 at 8:21 PM Tom Sommer wrote: I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg and /var/log/messages are getting flooded by these errors: lmtp[45758]:

Re: lmtp segfault after upgrade

2017-05-02 Thread Tom Sommer
On 2017-05-01 19:26, Aki Tuomi wrote: On May 1, 2017 at 8:21 PM Tom Sommer wrote: I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg and /var/log/messages are getting flooded by these errors: lmtp[45758]: segfault at 21 ip 7fb412d3ad11 sp

Re: lmtp segfault after upgrade

2017-05-02 Thread Aki Tuomi
On 2017-05-02 10:02, Tom Sommer wrote: On 2017-05-01 19:34, Aki Tuomi wrote: On May 1, 2017 at 8:26 PM Aki Tuomi wrote: > On May 1, 2017 at 8:21 PM Tom Sommer wrote: > > > I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg >

Re: lmtp segfault after upgrade

2017-05-02 Thread Tom Sommer
On 2017-05-01 19:34, Aki Tuomi wrote: On May 1, 2017 at 8:26 PM Aki Tuomi wrote: > On May 1, 2017 at 8:21 PM Tom Sommer wrote: > > > I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg > and /var/log/messages are getting flooded

Re: lmtp segfault after upgrade

2017-05-01 Thread Aki Tuomi
> On May 1, 2017 at 8:26 PM Aki Tuomi wrote: > > > > > On May 1, 2017 at 8:21 PM Tom Sommer wrote: > > > > > > I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg > > and /var/log/messages are getting flooded by these errors: > >

Re: lmtp segfault after upgrade

2017-05-01 Thread Aki Tuomi
> On May 1, 2017 at 8:21 PM Tom Sommer wrote: > > > I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg > and /var/log/messages are getting flooded by these errors: > > lmtp[45758]: segfault at 21 ip 7fb412d3ad11 sp 7ffe83ad2df0 > error 4 in