Comment 15 for bug 1690485

Hello Kevin, I don't want to step on Colin's toes here, but I couldn't sort out anything from the logs or files so far. I've had success before with perf to grab call graph information. The usual process is along the lines of:

- enable the ddebs.ubuntu.com repository to get access to debug symbols: https://wiki.ubuntu.com/Debug%20Symbol%20Packages

- install packages openssh-server-dbgsym libc6-dbgsym .. as needed

- Record perf results during testing with something like:
  sudo perf record -e syscalls:sys_enter_socket -R -a --call-graph dwarf sleep 20

- test

- Check results with something like:
  sudo perf script

With luck this will spit out the function names of the call chain at the time of the socket() syscall that is being killed (probably alongside a lot of unrelated instances -- it's possible to tune the perf line to narrow it down if necessary).

I hope this helps,
Thanks