Package: sipsak
Version: 0.9.8.1-1
Followup-For: Bug #1023739
Dear Maintainer,
This problem is still existing in Bullseye as well as in the next stable
Bookworm
-- System Information:
Debian Release: 11.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500,
Dear Maintainer,
I could reproduce a crash inside a
minimal Bookworm/testing amd64 qemu VM.
There I took below backtrace [2].
Having msg_data->repl_buff equal NULL seems to be the issue.
Upstream commit [1] looks related and a package built
with this commit does not crash with the example
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"...,
Package: sipsak
Version: 0.9.8.1-1
Severity: important
Dear Maintainer,
Running the following command on Bullseye causes a segmentation fault, whereas
running the same command on Stretch or Buster does not:
sipsak -M -B Hi -c sip:[From user]@[From host] -s sip:[To user]@[To host]
-- System
4 matches
Mail list logo
