This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: tst-getaddrinfo4 failure with glibc-2.18
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Allin Cottrell <cottrell at wfu dot edu>
- Cc: libc-help at sourceware dot org
- Date: Tue, 10 Sep 2013 09:55:56 -0400
- Subject: Re: tst-getaddrinfo4 failure with glibc-2.18
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot LNX dot 2 dot 03 dot 1308141222580 dot 1968 at wfu dot edu> <CAE2sS1jURE7KJCMbLqkZeQHLz5N5LV2ygY8CXBWosL0+NfRY8A at mail dot gmail dot com> <alpine dot LFD dot 2 dot 03 dot 1308141606420 dot 2742 at wfu dot edu> <alpine dot LFD dot 2 dot 03 dot 1308141624190 dot 3078 at wfu dot edu> <520BE867 dot 5060304 at redhat dot com> <alpine dot LNX dot 2 dot 03 dot 1308151104040 dot 652 at wfu dot edu> <alpine dot LNX dot 2 dot 03 dot 1308151234310 dot 554 at wfu dot edu> <522E011D dot 6000803 at redhat dot com> <alpine dot LNX dot 2 dot 03 dot 1309100911360 dot 617 at wfu dot edu>
On 09/10/2013 09:22 AM, Allin Cottrell wrote:
> I always run the test suite and pay attention to the results.
Allin, That's music to my ears. Thank you for reporting that,
and thank you for following our expected practice. Thank you
also for participating in the glibc community.
> I put "fix" in scare quotes above, because the lengthy discussion
> following Allan McRae's libc-alpha posting suggests that right fix is
> not obvious. But as an empirical matter it "works for me". In terms
> of diagnosing the problem I don't think I have anything to add to
> that discussion other than this data-point: I also had crashes in
> __strstr_sse42 with out-of-the-box glibc 2.18 on i686, and they've
> stopped after patching strstr.c as stated.
I'm sorry that this issue caused you to have problems. As a distribution
maintainer I see this pain also (I'm part of the team that maintains
Fedora's glibc, and RHEL's glibc).
I've added more information here:
https://sourceware.org/glibc/wiki/Release/2.18#Packaging_Changes
Does that capture what you saw and concluded?
Cheers,
Carlos.