[exim-dev] [Bug 2648] Use of $authres in a router headers_ad…

Página Inicial
Delete this message
Reply to this message
Autor: admin
Data:  
Para: exim-dev
Assunto: [exim-dev] [Bug 2648] Use of $authres in a router headers_add causes segmentation violation for local messages
https://bugs.exim.org/show_bug.cgi?id=2648

--- Comment #11 from Jim Fenton <fenton@???> ---
Finally figured how to actually get the symbols in gdb (previous backtrace was
from coredumpctl):

(gdb) print authenticated_id
$1 = (uschar *) 0x55e990c94aa0 "fenton"
(gdb) print sender_host_auth_pubname
$2 = (uschar *) 0x0

And a more complete backtrace from gdb:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:120
120    ../sysdeps/x86_64/multiarch/../strlen.S: No such file or directory.
(gdb) bt
#0  __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:120
#1  0x000055e9908d6313 in string_cat (s=<optimized out>, string=0x55e990cf42f8)
at string.c:1253
#2  string_append (string=0x55e990cf42f8, count=0, count@entry=2) at
string.c:1253
#3  0x000055e9908cfc1c in authres_smtpauth (g=<optimized out>) at
smtp_in.c:5955
#4  0x000055e99088b2f2 in expand_string_internal
(string=string@entry=0x55e990cf42d0 "${authresults {$primary_hostname}}", 
    ket_ends=ket_ends@entry=0, left=left@entry=0x0, skipping=skipping@entry=0,
honour_dollar=honour_dollar@entry=1, 
    resetok_p=resetok_p@entry=0x0) at expand.c:4346
#5  0x000055e990887b12 in expand_cstring (string=0x55e990cf42d0 "${authresults
{$primary_hostname}}") at expand.c:7986
#6  expand_cstring (string=0x55e990cf42d0 "${authresults {$primary_hostname}}")
at expand.c:7976
#7  0x000055e9908f7388 in rf_get_munge_headers (addr=addr@entry=0x55e990cabcc0,
rblock=rblock@entry=0x55e990c6ce80, 
    extra_headers=extra_headers@entry=0x7fff6d15e800,
remove_headers=remove_headers@entry=0x7fff6d15e7f8) at
rf_get_munge_headers.c:45
#8  0x000055e9908f2edd in accept_router_entry (rblock=0x55e990c6ce80,
addr=0x55e990cabcc0, pw=0x7fff6d15e8c0, verify=0, 
    addr_local=0x55e99097f968 <addr_local>, addr_remote=0x55e99097f958
<addr_remote>, addr_new=0x55e99097f960 <addr_new>, 
    addr_succeed=0x55e99097f948 <addr_succeed>) at accept.c:122
#9  0x000055e9908bf5a3 in route_address (addr=addr@entry=0x55e990cabcc0,
paddr_local=paddr_local@entry=0x55e99097f968 <addr_local>, 
    paddr_remote=paddr_remote@entry=0x55e99097f958 <addr_remote>,
addr_new=addr_new@entry=0x55e99097f960 <addr_new>, 
    addr_succeed=addr_succeed@entry=0x55e99097f948 <addr_succeed>,
verify=verify@entry=0) at route.c:1687
#10 0x000055e99087c8a6 in deliver_message (id=id@entry=0x55e990c72909
"1kYfHS-0005mk-1w", forced=forced@entry=0, 
    give_up=give_up@entry=0) at deliver.c:6824
#11 0x000055e9908a9900 in queue_run (start_id=0x0, stop_id=<optimized out>,
recurse=0) at queue.c:652
#12 0x000055e9908663f8 in main (argc=2, cargv=0x7fff6d19f3c8) at exim.c:4536


--
You are receiving this mail because:
You are on the CC list for the bug.