On 7/12/2012 10:27 PM, Eray Aslan wrote:
dovecot-2.1.8 sieve-0.3.1 binutils-2.22
When dovecot and sieve is linked with ld.gold I get a segfault in
checkscript command:
$ telnet localhost 4190
[some output]
authenticate "PLAIN" "<base64_username_password>"
[some more output]
checkscript "foobarscript"
connection closed
Logs:
2012-07-12T19:30:23.624158+00:00 bob dovecot: master: Dovecot v2.1.8
starting up
2012-07-12T19:31:22.548913+00:00 bob dovecot: managesieve-login: Login:
user=<username>, method=PLAIN, rip=192.168.122.1, lip=192.168.122.64,
mpid=12169, session=<YGo2AqfEcwDAqHoB>
2012-07-12T19:31:34.636747+00:00 bob dovecot: managesieve(username):
Fatal: master: service(managesieve): child 12169 killed with signal 11
(core dumped)
Based on your excellent bug report, I fixed this one yesterday:
http://hg.rename-it.nl/dovecot-2.1-pigeonhole/rev/6ceeb6421231
make check also fails (thank you for that):
[...]
Test case: ./tests/execute/errors.svtest:
1: Test 'Action conflicts: reject <-> fileinto' SUCCEEDED
2: Test 'Action conflicts: reject <-> keep' SUCCEEDED
3: Test 'Action conflicts: reject <-> redirect' SUCCEEDED
4: Test 'Action limit' SUCCEEDED
5: Test 'Redirect limit' SUCCEEDED
/tmp/work/dovecot-2.1-pigeonhole-0.3.1/src/testsuite/.libs/lt-testsuite:
symbol lookup error:
/tmp/work/dovecot-2.1-pigeonhole-0.3.1/src/lib-sieve/.libs/libdovecot-sieve.so.0:
undefined symbol: mail_deliver_get_log_var_expand_table
make: *** [tests/execute/errors.svtest] Error 127
I can't reproduce this (on Debian stable). How exactly did you configure
dovecot sources to use ld.gold? I just installed the binutils-gold
package, but I get the impression that ld.gold may not actually be used.
Also, perhaps this is caused by a version difference (mine is GNU gold
(GNU Binutils for Debian 2.20.1-system.20100303) 1.9).
I get the impression that this is an LD bug, but I do like to be sure.
Regards,
Stephan.
