Interestingly rebuilding 265-3ubuntu2 with DEBUG enabled... the code path of do_child_atfork() isn't even hitting (no debug statements from that function emitted). do_child_atfork() is where the proposed fix touches.
Additionally, I backleveled my trusty VM to 264-2.2ubuntu4. The testreproducer didn't segfault there either.
@BryanQuigley: Are you able to reproduce this bug? I may have to rely up on you or the reporter to test if so. The fix is straight-forward/upstream.. I'm just loathe to fix something that i can't prove fixes anything..
Interestingly rebuilding 265-3ubuntu2 with DEBUG enabled... the code path of do_child_atfork() isn't even hitting (no debug statements from that function emitted). do_child_atfork() is where the proposed fix touches.
Additionally, I backleveled my trusty VM to 264-2.2ubuntu4. The testreproducer didn't segfault there either.
@BryanQuigley: Are you able to reproduce this bug? I may have to rely up on you or the reporter to test if so. The fix is straight- forward/ upstream. . I'm just loathe to fix something that i can't prove fixes anything..