This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Understanding why getaddrinfo_a and __gai_enqueue_request use recursive locks
- From: Florian Weimer <fweimer at redhat dot com>
- To: Hal Murray <hmurray at megapathdsl dot net>, Carlos O'Donell <carlos at redhat dot com>
- Cc: libc-help at sourceware dot org
- Date: Mon, 25 Sep 2017 22:39:21 +0200
- Subject: Re: Understanding why getaddrinfo_a and __gai_enqueue_request use recursive locks
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx08.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx08.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 8D05EC0587E6
- References: <20170925172352.3634940605C@ip-64-139-1-69.sjc.megapath.net>
On 09/25/2017 07:23 PM, Hal Murray wrote:
I think you would need a way to annotate helper functions as needing a lock
and specify the lock. It may also take annotations in the caller function.
Do you mean annotations to find resource leaks?
As far as free software tools are concerned, using C++ and RAII looks
like the only feasible solution (with strong tool support) right now.
Florian