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: Understanding why getaddrinfo_a and __gai_enqueue_request use recursive locks

From: Florian Weimer <fweimer at redhat dot com>
To: Carlos O'Donell <carlos at redhat dot com>, Hal Murray <hmurray at megapathdsl dot net>
Cc: libc-help at sourceware dot org
Date: Mon, 25 Sep 2017 22:38:00 +0200
Subject: Re: Understanding why getaddrinfo_a and __gai_enqueue_request use recursive locks
Authentication-results: sourceware.org; auth=none
Authentication-results: ext-mx07.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-results: ext-mx07.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=fweimer at redhat dot com
Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 1DC04C047B71
References: <20170925172352.3634940605C@ip-64-139-1-69.sjc.megapath.net> <02a958e7-aafa-37e9-d1f0-8a0691be907f@redhat.com>

On 09/25/2017 09:06 PM, Carlos O'Donell wrote:

For glibc you can't use gcov (since some of the pieces of dependent functionality
are implemented by glibc),

We have special builds with profiling enabled. They should givefunction-level coverage information at least.


Florian

References:
- Re: Understanding why getaddrinfo_a and __gai_enqueue_request use recursive locks
  - From: Hal Murray
- Re: Understanding why getaddrinfo_a and __gai_enqueue_request use recursive locks
  - From: Carlos O'Donell

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