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: "Carlos O'Donell" <carlos at systemhalted dot org>, libc-help at sourceware dot org
- Date: Wed, 14 Aug 2013 16:28:23 -0400
- Subject: Re: tst-getaddrinfo4 failure with glibc-2.18
- 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>
On 08/14/2013 04:25 PM, Allin Cottrell wrote:
> On Wed, 14 Aug 2013, Allin Cottrell wrote:
>
>> On Wed, 14 Aug 2013, Carlos O'Donell wrote:
>>
>>> On Wed, Aug 14, 2013 at 12:26 PM, Allin Cottrell <cottrell@wfu.edu> wrote:
>>>> I've just built glibc-2.18 on an i686 system with gcc-4.8.1. Under "make
>>>> check" I'm getting a failure on tst-getaddrinfo4, and I'm wondering if
>>>> that's anything to get excited about.
>>>>
>>>> The file tst-getaddrinfo4.out reads as follows:
>>>>
>>>> SUCCESS getaddrinfo(service=NULL, family=0, flags=0): Unknown error: Success
>>>> SUCCESS getaddrinfo(service=NULL, family=0, flags=32): Unknown error:
>>>> Success
>>>> SUCCESS getaddrinfo(service=NULL, family=2, flags=0): Unknown error: Success
>>>> SUCCESS getaddrinfo(service=NULL, family=10, flags=0): Unknown error:
>>>> Success
>>>> FAIL getaddrinfo(service=http, family=0, flags=0): Servname not supported
>>>> for ai_socktype: Success
>>>> FAIL getaddrinfo(service=http, family=0, flags=32): Servname not supported
>>>> for ai_socktype: Success
>>>> FAIL getaddrinfo(service=http, family=2, flags=0): Servname not supported
>>>> for ai_socktype: Success
>>>> FAIL getaddrinfo(service=http, family=10, flags=0): Servname not supported
>>>> for ai_socktype: Success
>>>
>>> Any failure is something to get excited about. An i686 build should
>>> have no failures in the testsuite.
>>>
>>> You'll have to dig into the test to see exactly what it expects and
>>> what is failing.
>>
>> Can you suggest a place to start digging? I've tried googling the error message + glibc [...]
>
> Sorry, kinda silly question. I've started looking at the code for
> this test (a new one, I see) and trying to understand what it's
> doing.
You want to look at glibc/posix/tst-getaddrinfo4.c.
Reading up on the related bug is probably a good idea.
The bug is referenced in the test, and you can find it
in the sourceware bugzilla e.g. http://sourceware.org/bugzilla/.
Cheers,
Carlos.