Bug#987916: openssh: Segfault or malloc_consolidate(): invalid chunk size + Aborted with GSSAPITrustDns yes
Hello Chris,
I am not involved in packaging, just trying to give some
pointers to get better information for the maintainers.
In [1] are several possible actions listed, that could be
used to get more informations.
Just to clarify, host heisenberg is your local system,
from which the connection starts?
If yes, I would propose these actions:
- If possible, install systemd-coredump. Then in the journalctl
output there should already appear a basic backtrace with
a crashing process, plus a core gets collected of it and
stored for some time (e.g. "coredumpctl list" or "coredumpctl gdb").
- Try connecing setting following environment before:
export MALLOC_CHECK_=3
That should make stricter checks in the allocator
and maybe fail earlier.
- You might install debug symbols too, also described in [1].
With that you could also start the connection inside a debugger:
gdb -q --args ssh hammercloud-ai-11.cern.ch -v
And do following actions at the gdb prompt:
run
bt
detach
quit
That way the 'bt' command should print a backtrace
that might help to reproduce the issue.
Kind regards,
Bernhard
[1] https://wiki.debian.org/HowToGetABacktrace
Reply to: