I'm getting a segmentation fault running an intentionally "esoteric" 
installation of exim.

It is a requirement to use a specific configuration file for each instance of 
exim we have running. (After the security changes which were introduced in 
4.72, this setup is more difficult to accomplish - or may not be possible at 
all).

To recreate:
Copy a valid exim configuration to dir.
# cp /etc/exim/exim.conf /sharedfolder/
Then run exim.
/usr/sbin/exim  -v -C /sharedfolder/exim.conf charl...@neptuneweb.com
Get Segmentation fault
I've seen this happen when exim is invoked as root or non-root.

Running gdb, I get:

$ gdb /usr/sbin/exim
GNU gdb (GDB) Red Hat Enterprise Linux (7.2-48.el6)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/sbin/exim...(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install exim-4.72-2.el6.x86_64
(gdb) set follow-fork-mode child
(gdb) r  -v -C /tmp/exim.conf c...@neptuneweb.com
Starting program: /usr/sbin/exim -v -C /tmp/exim.conf c...@neptuneweb.com
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x00007fe90fd760c2 in __strlen_sse2 () from /lib64/libc.so.6
(gdb) bt
#0  0x00007fe90fd760c2 in __strlen_sse2 () from /lib64/libc.so.6
#1  0x00007fe91263dc2f in string_vformat ()
#2  0x00007fe91260ddd1 in log_write ()
#3  0x00007fe9125f617c in main ()
(gdb) q

I also compiled a local version of exim - to enable debug symbols - alas the 
problem doesn't occur. (This, local, compilation is not exactly the same as my 
RedHat installation (RPM) - I can do that - but thought I'd ask if anyone has 
seen this before I try.)

Thanks,

----
Charlie M. Dalsass
Neptune Web, Inc.

-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##

Reply via email to