> Well, I already answered you that this bug exists in glibc 2.30 but not 2.31 > which is why I uploaded glibc 2.31 to unreleased for sparc64. > > I have not verified yet whether this commit fixes the problem, but I assume > it's a commit that is part of the working 2.31 and not in 2.30 branch. Ah sorry. I didn't know the exact glibc version off of my head, so I couldn't quite catch the meaning of your reply. Thanks for the clarification.