From: Florian Weimer <fweimer@redhat.com>
To: Hal Murray <hmurray@megapathdsl.net>,
Carlos O'Donell <carlos@redhat.com>
Cc: libc-help@sourceware.org
Subject: Re: Understanding why getaddrinfo_a and __gai_enqueue_request use recursive locks
Date: Mon, 25 Sep 2017 20:39:00 -0000 [thread overview]
Message-ID: <34cdf978-e9ca-b401-9bbf-af0d4cd84d4f@redhat.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2017-09-25 20:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 7:08 Will Hawkins
2017-09-23 13:04 ` Carlos O'Donell
2017-09-23 14:44 ` Will Hawkins
2017-09-25 16:13 ` Carlos O'Donell
2017-09-25 17:05 ` Will Hawkins
2017-09-25 17:23 ` Hal Murray
2017-09-25 19:06 ` Carlos O'Donell
2017-09-25 20:38 ` Florian Weimer
2017-09-25 20:39 ` Florian Weimer [this message]
2017-09-26 6:29 ` Hal Murray
2017-09-25 23:00 ` Will Hawkins
2017-09-26 4:42 ` Carlos O'Donell
2017-09-26 6:06 ` Will Hawkins
2017-09-26 18:39 ` Will Hawkins
2017-09-27 5:54 ` Carlos O'Donell
2017-09-27 6:02 ` Will Hawkins
2017-09-27 6:05 ` Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=34cdf978-e9ca-b401-9bbf-af0d4cd84d4f@redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=hmurray@megapathdsl.net \
--cc=libc-help@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).