21 Nov
2021
21 Nov
'21
8:50 p.m.
On Nov 21, 2021, at 8:42 PM, Norman Elton <normelton@gmail.com> wrote:
Here's the mystery ... this is reproducible in 3.0.20, but is seemingly fixed in 3.0.21. I reviewed the release notes for 3.0.21, and don't see anything obviously related. Can anyone confirm this was actually fixed, versus something that might reappear one day?
If it were a minor bug, I probably wouldn't care. But a segfault is worth a little more digging.
It's fixed. You can always run "gdb" to see where it crashes, and verify that the code has changed. You should probably also be running 3.0.25. See http://packages.networkradius.com Alan DeKok.