https://bugs.exim.org/show_bug.cgi?id=2648
--- Comment #9 from Jim Fenton <fen...@bluepopcorn.net> ---
After much learning about how to enable coredumps and get symbols I have it.
Here's the backtrace; if you need the core file itself I can send it to you.
root@altmode:~# coredumpctl dump 2627 -o exim4.core.2627
PID: 2627 (exim4)
UID: 0 (root)
GID: 109 (Debian-exim)
Signal: 11 (SEGV)
Timestamp: Sat 2020-10-31 15:47:08 PDT (7min ago)
Command Line: /usr/sbin/exim4 -qG
Executable: /usr/sbin/exim4
Control Group: /system.slice/exim4.service
Unit: exim4.service
Slice: system.slice
Boot ID: d15983a39f194ce390859bdfe9d4e344
Machine ID: 458e5ad9c19ace0873fd2d7df75e74c4
Hostname: altmode.net
Storage:
/var/lib/systemd/coredump/core.exim4.0.d15983a39f194ce390859bdfe9d4e344.2627.1604184428000000.lz4
Message: Process 2627 (exim4) of user 0 dumped core.
Stack trace of thread 2627:
#0 0x00007f27ebc6e206 __GI___strlen_sse2 (libc.so.6)
#1 0x000055e9908d6313 string_cat (exim4)
#2 0x000055e9908cfc1c authres_smtpauth (exim4)
#3 0x000055e99088b2f2 expand_string_internal (exim4)
#4 0x000055e990887b12 expand_cstring (exim4)
#5 0x000055e9908f7388 rf_get_munge_headers (exim4)
#6 0x000055e9908f2edd accept_router_entry (exim4)
#7 0x000055e9908bf5a3 route_address (exim4)
#8 0x000055e99087c8a6 deliver_message (exim4)
#9 0x000055e9908a9900 queue_run (exim4)
#10 0x000055e9908663f8 main (exim4)
#11 0x00007f27ebbfa09b __libc_start_main (libc.so.6)
#12 0x000055e99086818a _start (exim4)
--
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
details at http://www.exim.org/ ##
