https://bugs.exim.org/show_bug.cgi?id=2274
--- Comment #19 from Alex <alexey@???> ---
Sorry to say that, the patch did not help. Another crash happened recently on
- 2018-06-04 12:00:10 at 14:27
Seems to be all the same:
[root@server ccpp-2018-06-04-12:00:10-14027]# gdb /usr/sbin/exim coredump
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-110.el7
Copyright (C) 2013 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...done.
[New LWP 14027]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/sbin/exim -oMr spam-scanned -bS'.
Program terminated with signal 11, Segmentation fault.
#0 __strncpy_sse2_unaligned () at
../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:296
296 movdqu (%rsi), %xmm1
(gdb) bt
#0 __strncpy_sse2_unaligned () at
../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:296
#1 0x00000000004269f6 in main (argc=4, cargv=<optimized out>) at exim.c:4093
(gdb) frame 0
#0 __strncpy_sse2_unaligned () at
../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:296
296 movdqu (%rsi), %xmm1
(gdb) frame 1
#1 0x00000000004269f6 in main (argc=4, cargv=<optimized out>) at exim.c:4093
4093 Ustrncpy(p + 4, initial_cwd, big_buffer_size-5);
(gdb)
And I'm sure the exim was patched:
[root@server directadmin]# ls -la `which exim`
-rwsr-xr-x 1 root root 3981672 May 29 08:36 /sbin/exim
[root@server directadmin]# ls -la
/usr/local/directadmin/custombuild/exim-4.91-patched/src/exim.c
-rw-r--r-- 1 root root 179138 May 29 08:32
/usr/local/directadmin/custombuild/exim-4.91-patched/src/exim.c
Please advice.
Regards,
Alex.
--
You are receiving this mail because:
You are on the CC list for the bug.
