Autor: Juha Saarinen Data: A: Exim-Users@Exim. Org Assumpte: [Exim] Exim (probably Perl in actual fact) problems with FreeBSD 4.3
Looks like that Perl issue with the FreeBSD port of Exim is coming back to
haunt me. Upgraded a 4.2-STABLE box to 4.3-STABLE; it was running Exim 3.20.
After reboot, Exim started fine, but I noticed some old frozen messages that
I wanted to thaw... no go:
# exim -bp
/usr/libexec/ld-elf.so.1: Undefined symbol "PL_stack_max" referenced from
COPY relocation in exim
bash-2.04# exim -M
/usr/libexec/ld-elf.so.1: Undefined symbol "PL_stack_max" referenced from
COPY relocation in exim
bash-2.04# exim -Mt
/usr/libexec/ld-elf.so.1: Undefined symbol "PL_stack_max" referenced from
COPY relocation in exim
# exim
/usr/libexec/ld-elf.so.1: Undefined symbol "PL_stack_max" referenced from
COPY relocation in exim
"PL_stack_max" looks like a Perl thingy.
Upgrading Exim to 3.22 produced the now familiar:
# exim -d9 -bd -q30m
Exim version 3.22 debug level 9 uid=0 gid=0
probably Berkeley DB version 1.8x (native mode)
Caller is an admin user
Caller is a trusted user
originator: uid=0 gid=0 login=root name=Rootster Root
port = 25
listening on all interfaces
Segmentation fault
Arrgh. I'm guessing this isn't an Exim issue, but some buglet caused by Perl
on FreeBSD.
Will investigate further.
--
Juha
The malformed orange
Fails to satisfy the eye:
Segmentation fault.
