This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: getaddrinfo thread-safe?

From: Joshua Rogers <glibc at internot dot info>
To: libc-help at sourceware dot org
Date: Tue, 24 Mar 2015 07:05:14 +1100
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> <551044FC dot 9010403 at redhat dot com> <55104A76 dot 40201 at internot dot info> <5510673A dot 5040408 at redhat dot com> <55106E62 dot 3070007 at internot dot info>

On 24/03/15 06:49, Joshua Rogers wrote:
> In thread 4, pthread_mutex_lock is called on 'lock', on L127 of
> files-hosts.c. That's all OK:   __libc_lock_lock (lock);
>
> But then, it is unlocked in thread 3? I don't understand that.
Ah, Nevermind. I really am tired!!

'lock' was fired read here:
==30720==    by 0x6030486: _nss_files_gethostbyname3_r (files-hosts.c:127)


It was then subsequently read here:
==30720==    by 0x4C30E75: ??? (in
/usr/lib/valgrind/vgpreload_drd-amd64-linux.so)


This is probably a bug in valgrind.



-- 
-- Joshua Rogers <https://internot.info/>

Attachment: signature.asc
Description: OpenPGP digital signature

Follow-Ups:
- Re: getaddrinfo thread-safe?
  - From: Joshua Rogers

References:
- getaddrinfo thread-safe?
  - From: Joshua Rogers
- Re: getaddrinfo thread-safe?
  - From: Carlos O'Donell
- Re: getaddrinfo thread-safe?
  - From: Joshua Rogers
- Re: getaddrinfo thread-safe?
  - From: Carlos O'Donell
- Re: getaddrinfo thread-safe?
  - From: Joshua Rogers
- Re: getaddrinfo thread-safe?
  - From: Carlos O'Donell
- Re: getaddrinfo thread-safe?
  - From: Joshua Rogers

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]