Re: Crash problem

managed to produce a SIGSEGV so i now have a core file, this is what i get

ore was generated by `/usr/exim/bin/exim-4.99-2 -qq'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007f7b17bdf622 in strlen () from /lib64/libc.so.6
(gdb) bt
#0  0x00007f7b17bdf622 in strlen () from /lib64/libc.so.6
#1  0x00000000004558d6 in ?? ()
#2  0x00000c5c009109e0 in ?? ()
#3  0x0000000000651860 in ?? ()
#4  0x0000000000000000 in ?? ()

On 2025-11-04 11:00, Jeremy Harris via Exim-users wrote:
> OK, that didn't detect anything.  We need to investigate a core.
>
> Do a build with "CFLAGS += -O0 -ggdb".
>
> Does Slackware have the systemd-ish coredumpctl stuff?
> I suspect not; so we need to enable suid-coredumps.
>  (Over here, Fedora, the hints are in "man core" which mentions 
> /proc/sys/fs/suid_dumpable)
> and check that "ulimit" does not restrict the size of corefile.
>
> Run a test to get a crash, and locate the core file.
>
> Run up gdb - "sudo gdb <exim-binary-location> <corefile-location>".
>   Ignore all the offers to load debuginfo file for libraries.
>   At the prompt:   "bt"
> You should get a more comprehensive stacktrace, with file and line 
> number info.
>
>
> Copy that here.  Keep the corefile; we may want to pull some
> variable values out of it.
>
> (If you can do IRC, I'm in #exim on irc.libera.chat)

-- 
## subscription configuration (requires account):
##   https://lists.exim.org/mailman3/postorius/lists/exim-users.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/