Date: Thu, 7 Oct 2021 14:14:56 -0400 From: Kurt Hackenberg <kh@panix.com> To: questions@freebsd.org Subject: Re: How do I get a coredump file from an application? Message-ID: <c0df8705-f82d-0736-fe0f-f03d74c83391@panix.com> In-Reply-To: <20211007062941.bf0f53fa571b041064a6d931@sohara.org> References: <CAAdA2WPSfnbWLi3FZYmqONCYGg_7wgEObq8TzKbaY-cd8G13yw@mail.gmail.com> <ba885bec-33e7-c935-3a3a-b6138e4f7447@panix.com> <CAAdA2WOviDitn6NJiAEgc65XzyK30Zd3Xq8K1NiWqDTeWjLj6g@mail.gmail.com> <YV5kktlieKXBTmVM@rain.home> <20211007062941.bf0f53fa571b041064a6d931@sohara.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021/10/07 01:29, Steve O'Hara-Smith wrote: >> If Exim catches that signal, then the only way to get a coredump is to >> make Exim not catch that signal -- that is, temporarily remove the >> call to signal() or sigaction(). > > There are a number of signals you can send to cause a core dump > SIGABORT usually works, SIGFPE is almost never caught. Sure, but that wouldn't catch the bug that's being chased: Exim uses an invalid address, and the OS notifies the process by sending it the software signal SIGSEGV.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c0df8705-f82d-0736-fe0f-f03d74c83391>