[Bug 3158] SIGSEGV - null pointer indirection - daemon-accept handling TLS incoming connection
Exim Bugzilla via Exim-dev <[email protected]>
| Newsgroups | gmane.mail.exim.devel |
|---|---|
| Message-ID | <[email protected]/> |
https://bugs.exim.org/show_bug.cgi?id=3158 --- Comment #2 from [email protected] --- (In reply to Jeremy Harris from comment #1) > I assume this is the one you were suggesting "AI" could fix. Yes and no – same bug I had mentioned on IRC, but I have enough human intelligence to *never* suggest that so-called "AI" can fix anything. I was just experimenting, the day before such experiments helped me identify one specific line which caused failed assertion and core dump in mandoc. So when I got an Exim core, I was enthusiastic to threw it in as well. > Can you get a debug log, starting at least as far back as the start of > routing? No, I am afraid I cannot, as those errors are happening very infrequently. What is comment, though, is that they occur on cutthrough delivery, when sending host is *.google.com and destination is also *.google.com. -- You are receiving this mail because: You are on the CC list for the bug. -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-dev.lists.exim.org/ ## unsubscribe (doesn't require an account): ## [email protected] ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/