[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 Alex changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 Git Commit changed: What|Removed |Added CC||g...@exim.org --- Comment #21 from Git Commit ---

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 --- Comment #20 from Jeremy Harris --- (In reply to Alex from comment #15) > > Perhaps if os_getcwd() fails? Could it be that the spam-checker has > > chdir()'d to a directory which it unlinks, but calls Exim from inside, > > so that Exim's

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 --- Comment #19 from Alex --- 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

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 --- Comment #18 from Alex --- Hello Phil, Thanks for the patch, it's applied now. I will let you know results. It might take a while. Regards, Alex. -- You are receiving this mail because: You are on the CC list for the bug. -- ##

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 --- Comment #17 from Phil Pennock --- https://git.exim.org/exim.git/commitdiff/805fd869d551c36d1d77ab2b292a7008d643ca79 Alex, does applying this as a patch solve your problem? -- You are receiving this mail because: You are on the CC

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 Phil Pennock changed: What|Removed |Added Assignee|t...@duncanthrax.net |p...@exim.org

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 --- Comment #15 from Alex --- > Perhaps if os_getcwd() fails? Could it be that the spam-checker has > chdir()'d to a directory which it unlinks, but calls Exim from inside, > so that Exim's os_getcwd() fails? It seems:

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 --- Comment #14 from Alex --- Will the following help? [root@server ccpp-2018-05-15-15:38:54-18615]# gdb /usr/sbin/exim coredump GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-110.el7 Copyright (C) 2013 Free Software Foundation, Inc.

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 --- Comment #13 from Alex --- Hello Phil, Directadmin manages Exim the following way: 1. at a moment of installation of a new server a pre-compiled package is installed from DA's repository, it's called da_exim for CentOS. 2. then

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 Phil Pennock changed: What|Removed |Added CC||p...@exim.org --- Comment #12

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 --- Comment #11 from Alex --- So in this case I need to start a gdb session and feed the process of `/usr/sbin/exim -oMr spam-scanned -bS` with an email which caused the crash. If this is the case... we don't have the email

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 --- Comment #10 from Jeremy Harris --- Something else; that doesn't include a stack trace -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 --- Comment #9 from Alex --- Do you mean the one that attached as an attachment 1086? Or something else different? Regards, Alex. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 --- Comment #8 from Jeremy Harris --- Unhelpful. We need the stack trace. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 --- Comment #5 from Alex --- Hello Heiko, Thanks for your reply. (In reply to Heiko Schlittermann from comment #1) > So, the next time the same message is delivered via the same transport, it > does not segfault? Yes, as soon as we

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 --- Comment #6 from Alex --- Hello Jeremy, Thanks for your reply. (In reply to Jeremy Harris from comment #4) > To get more info, configure your system to take corefiles (see "man core", > including the setuid specifics), and install

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 Heiko Schlittermann changed: What|Removed |Added CC|

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 --- Comment #4 from Jeremy Harris --- To get more info, configure your system to take corefiles (see "man core", including the setuid specifics), and install the debuginfo package for glibc. Once you have a coredump, run (as root)

[exim-dev] [Bug 2274] exim 4.91: segfault ... error 4 in libc-2.17.so

https://bugs.exim.org/show_bug.cgi?id=2274 --- Comment #2 from Heiko Schlittermann --- Do you know how to enable core dumps on set-uid binaries? This could help for further tracing. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List