This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: getaddrinfo thread-safe?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Joshua Rogers <glibc at internot dot info>, libc-help at sourceware dot org
- Date: Mon, 23 Mar 2015 12:53:16 -0400
- Subject: Re: getaddrinfo thread-safe?
- Authentication-results: sourceware.org; auth=none
- References: <5510006C dot 1020908 at gmail dot com> <551030EF dot 1020504 at redhat dot com> <551035E5 dot 30103 at internot dot info>
On 03/23/2015 11:48 AM, Joshua Rogers wrote:
> On 24/03/15 02:27, Carlos O'Donell wrote:
>> Please debug a bit further and see if you can suss out what's actually
>> going on and which writes are conflicting. Your sources don't appear to
>> line up with master, so I would suggest a simple test case using:
>> -Wl,--dynamic-linker and -Wl,-rpath.
> I'm unable to use the master version of glibc, as I don't know how to
> compile it, and use it.
> I am, however, using eglib on Ubuntu, which is inevitably outdated.
> Could you compile the source I linked, and run the valgrind on it,
> using the latest glibc?
Does this help?
https://sourceware.org/glibc/wiki/Testing/Builds
> In the code of reopen:
>> static int
>> reopen (res_state statp, int *terrno, int ns)
>
>> __have_o_nonblock
>> = (EXT(statp).nssocks[ns] == -1
>> && errno == EINVAL ? -1 : 1);
> And that is why it complains, probably.
>
> Please check the vanilla glibc code.
The code is still there, but you still need to show what is happening.
Why does hellgrind think there is a race condition there, and does
it make sense.
Cheers,
Carlos.