Dear Bill, dear Héctor,
I am also experiencing this issue, and I may be able to narrow it down a
bit further.
Specifically, I have two different stretch machines, only one of which
has this issue.
The two machines are very similar in terms of software: one was last
upgraded in early
Septemberwhile the other was only installed about two weeks ago. As for
the underlying
hardware (these are VMs), there are some differences; most notably, they
use a different
CPU (Intel E5-2680v4 vs. Intel 6140). The minimal example works fine on
the former VM
and fails with the stated message on the latter.
The two machines use identical versions of almost all installed
packages, including
gdb (7.12-6) and libc6 (2.24-11+deb9u3). There are only few exceptions,
most of which
seem completely unrelated (e.g. slightly different versions of Python
and git). There
is however one important difference, and that's the kernel: the working
machine is
running linux-image-4.9.0-8-amd64 (4.9.110-3+deb9u4) while the "broken"
one uses
linux-image-4.9.0-7-amd64 (4.9.110-3+deb9u2).
Unfortunately, I cannot test at this time whether upgrading the kernel
on the "broken"
machine fixes the issue due to long-running processes. I will report
back once I get
a chance to do so.
Cheers,
JAA
