Bug#1023739: sipsak: Message mode causes segmentation fault

[Yannick McCabe-Costa]

Interestingly, reviewing a strace of the command you published, it seems 
to be when the system is parsing /etc/hosts

Clearing all entries in this file allows the application to continue 
past the segfault, only to fail at resolving the hostname:

write(2, "error: cannot resolve local host"..., 51error: cannot resolve 
local hostname: [REDACTED]

strace of the original command as reported:

mprotect(0x7f8574292000, 4096, PROT_READ) = 0
munmap(0x7f8574ac2000, 7030)            = 0
openat(AT_FDCWD, "/etc/hosts", O_RDONLY|O_CLOEXEC) = 5
lseek(5, 0, SEEK_CUR)                   = 0
fstat(5, {st_mode=S_IFREG|0644, st_size=23, ...}) = 0
read(5, "127.0.0.1 8f146307c8eb\n", 4096) = 23
lseek(5, 0, SEEK_CUR)                   = 23
read(5, "", 4096)                       = 0
close(5)                                = 0
brk(0x55e8d9c43000)                     = 0x55e8d9c43000
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---
+++ killed by SIGSEGV +++
Segmentation fault

[Wed Nov  9 13:28:01 2022] sipsak[67985]: segfault at 0 ip 
00007fe9a9005096 sp 00007fff550a4800 error 6 in 
libc-2.31.so[7fe9a8fb3000+15a000]

Could this be something related to name resolution/parsing within sipsak?