unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Martin Sebor <msebor@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] add support for -Wmismatched-dealloc
Date: Mon, 14 Dec 2020 23:16:57 +0100	[thread overview]
Message-ID: <87lfe09go6.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <758e723b-67cf-a211-7bc2-2ccd3fc744e5@gmail.com> (Martin Sebor's message of "Mon, 14 Dec 2020 14:39:56 -0700")

* Martin Sebor:

> Florian asked this morning if getaddrinfo() and freeaddrinfo() are
> covered by this change.  They're not because getaddrinfo() returns
> the allocated memory indirectly, via an argument.  To handle those
> kinds of APIs that return a pointer to the allocated object
> indirectly, through an argument, the attribute will need to be
> enhanced somehow.

asprintf is another such function, perhaps slightly more commonly used.
It would be nice if this interface pattern could be covered as well.

Thanks,
Florian
-- 
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill


  reply	other threads:[~2020-12-14 22:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 22:52 [PATCH] add support for -Wmismatched-dealloc Martin Sebor via Libc-alpha
2020-12-09  0:07 ` Joseph Myers
2020-12-12  2:25   ` Martin Sebor via Libc-alpha
2020-12-14 21:39     ` Martin Sebor via Libc-alpha
2020-12-14 22:16       ` Florian Weimer via Libc-alpha [this message]
2020-12-15  1:01       ` Joseph Myers
2020-12-15 16:52         ` Martin Sebor via Libc-alpha
2020-12-27 23:13           ` Martin Sebor via Libc-alpha
2021-01-04 15:56             ` Ping: " Martin Sebor via Libc-alpha
2021-01-04 16:07             ` Florian Weimer via Libc-alpha
2021-01-04 16:18               ` Martin Sebor via Libc-alpha
2021-01-04 16:57                 ` Florian Weimer via Libc-alpha
2021-01-04 23:18                   ` Martin Sebor via Libc-alpha
2021-01-10 20:42                     ` Ping: " Martin Sebor via Libc-alpha
2021-01-11  9:13                     ` Florian Weimer via Libc-alpha
2021-01-12  0:00                       ` Martin Sebor via Libc-alpha
2021-01-12  0:01                       ` Martin Sebor via Libc-alpha
2021-01-12  8:59                         ` Florian Weimer via Libc-alpha
2021-01-19  1:08                           ` Martin Sebor via Libc-alpha
2021-01-19 16:54                           ` David Malcolm via Libc-alpha
2021-01-22 21:26                         ` DJ Delorie via Libc-alpha
2021-01-25 10:56                         ` Florian Weimer via Libc-alpha
2021-01-25 11:31                         ` Florian Weimer via Libc-alpha
2021-04-23  0:00                         ` Martin Sebor via Libc-alpha
2021-05-06 23:54                           ` Martin Sebor via Libc-alpha
2021-05-13 21:49                             ` Martin Sebor via Libc-alpha
2021-05-16 21:25                               ` Martin Sebor via Libc-alpha

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lfe09go6.fsf@oldenburg2.str.redhat.com \
    --to=libc-alpha@sourceware.org \
    --cc=fweimer@redhat.com \
    --cc=msebor@gmail.com \
    /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).