"failed to map segment from shared object" in sieve pipe

[Dorian Taylor]

Hello,

I have encountered a problem attempting to run a program in a sieve pipe. The program is a Perl script that loads a number of binary (XS) modules at runtime. The program crashes, it appears, if it tries to load too many. The (non-Perl part of the) error message is "failed to map segment from shared object” — no additional information.

Cryptic error messages like this have the odour of imposed resource restrictions, so I’m wondering if there are any on the pipe/filter/execute implementation (e.g. via program_client_run).

Any configuration knobs I can twiddle? Any insights for debugging?

PS this is the dovecot 2.2.22 (fe789d2), the one that ships with Ubuntu Xenial.

Regards,

--
Dorian Taylor
Make things. Make sense.
https://doriantaylor.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://dovecot.org/pipermail/dovecot/attachments/20180321/725022ee/attachment-0001.sig>