dovecot-pigeonhole running external script ends with signal 11

[Tobi]

Hi Stephan

currently the rpm is built based on 0.4.14
Should I try with 0.4.16? I will build it again this afternoon with the version you suggested and report back with the results.

Thanks for the help here

tobi

----- Originale Nachricht -----
Von: Stephan Bosch <stephan at rename-it.nl>
Gesendet: 08.01.17 - 11:00
An: tobster at brain-force.ch@pgp.brain-force.ch,
	Dovecot Mailing List <dovecot at dovecot.org>
Betreff: Re: dovecot-pigeonhole running external script ends with signal 11

> Op 1/8/2017 om 10:00 AM schreef Tobi:
>> Hi Stephan
>>
>> according to ps aux the process that segfaults is (pid 18261)
>>
>> vmail    18261  0.0  0.0      0     0 pts/0    Z    09:39   0:00 [lmtp]
>> <defunct>
>>
>> the gdb backtrace I attached to my mail was the deepest one I got
> 
> That looks like it happens in Dovecot still.
> 
>> @Steffen
>> the script does not chroot, at least not that I'm aware of. I checked my
>> dovecot configs and could not find any active chroot config. All
>> occurences of mail_chroot are commented out and have no path values.
> 
> What about the version information I asked about?
> 
> Regards,
> 
> Stephan.
> 
>> Am 06.01.2017 um 00:04 schrieb Stephan Bosch:
>>> Op 1/4/2017 om 9:37 AM schreef Tobi:
>>>> Hi Aki
>>>>
>>>> yes I built dovecot and pigeonhole rpms in the same rpmbuild. pigeonhole
>>>> rpm is based on 0.4.14
>>>> Do you think that the error might come from self building the rpms?
>>> But what version of Pigeonhole are you actually using? Version 0.4.16 is
>>> released for Dovecot v2.2.26.
>>>
>>> Also:
>>>
>>> - Can you find out which process is getting the segfault? GDB shows the
>>> pid and you should lookup what process that is while GDB is still active.
>>> - Isn't that GDB backtrace you provided deeper? It shows only two
>>> levels, but that makes no sense (i.e. main() is not listed).
>>>
>>> Regards,
>>>
>>> Stephan.
>>>
>