https://bugs.exim.org/show_bug.cgi?id=1870
--- Comment #2 from Steve Hill <steve@???> ---
This is the stack trace dumped out by glibc. But I don't think it'll help
because it crashes out on free() due to heap corruption which happened some
time earlier.
Whether or not Valgrind understand's exim's memory allocation, I'm pretty sure
an "invalid write" really does mean its writing to memory that it shouldn't be.
*** glibc detected *** /usr/sbin/exim: double free or corruption (!prev):
0x00007f9715666080 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x303ca75f4e)[0x7f8ab1cdcf4e]
/lib64/libc.so.6(+0x303ca78cf0)[0x7f8ab1cdfcf0]
/lib64/libc.so.6(fclose+0x14d)[0x7f8ab1ccd4cd]
/usr/sbin/exim(+0x55de2)[0x7f8ab4584de2]
/usr/sbin/exim(+0x59eef)[0x7f8ab4588eef]
/usr/sbin/exim(+0x51055)[0x7f8ab4580055]
/usr/sbin/exim(+0x511cf)[0x7f8ab45801cf]
/usr/sbin/exim(+0x542c1)[0x7f8ab45832c1]
/usr/sbin/exim(expand_check_condition+0x26)[0x7f8ab4588906]
/usr/sbin/exim(route_address+0xb96)[0x7f8ab45b41d6]
/usr/sbin/exim(deliver_message+0x1132)[0x7f8ab456ddf2]
/usr/sbin/exim(queue_run+0xcc4)[0x7f8ab45a0274]
/usr/sbin/exim(main+0x3cd5)[0x7f8ab45793b5]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7f8ab1c85d5d]
/usr/sbin/exim(+0x2c539)[0x7f8ab455b539]
--
You are receiving this mail because:
You are on the CC list for the bug.
