Even though I agree with what you are saying, it is also worth looking at the issue through the eyes of the author. The function that they were calling can be

Even though I agree with what you are saying, it is also worth looking at the issue through the eyes of the author. The function that they were calling can be summarized as, "check to see if a value is in a set," only to receive an initially inexplicable segfault. They had a clear example of what that could look like, someone else's code from a common library, yet spent a considerable amount of time untangling the code in the library where the bug popped up. It is wrong to assume incompetence on the part of the glibc authors, particularly when the comparison library has a much more limited scope and can afford to avoid "bullshit code", but the source of the frustration is clear. I would hardly define them as an arrogant prick because of that.