From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [PATCH 0/3] a few more leak fixes
Date: Thu, 5 Oct 2023 17:28:02 -0400 [thread overview]
Message-ID: <20231005212802.GA982892@coredump.intra.peff.net> (raw)
I was really bothered that using clang with SANITIZE=leak found a leak
that gcc didn't. And then I was doubly bothered to find that there is
one that gcc finds that clang doesn't!
I don't think either of these are urgent or important leaks on their
own, but the flaky nature of the results makes it annoying while trying
to find and clean up other leaks. So here are some fixes. Patches 1 and
3 are those two cases, respectively. Patch 2 is a more interesting
leak-fix enabled by the infrastructure added in patch 1.
[1/3]: decorate: add clear_decoration() function
[2/3]: revision: clear decoration structs during release_revisions()
[3/3]: daemon: free listen_addr before returning
daemon.c | 37 ++++++++++++++++++--------------
decorate.c | 15 +++++++++++++
decorate.h | 10 +++++++++
line-log.c | 10 +++++++++
line-log.h | 2 ++
revision.c | 9 ++++++++
t/helper/test-example-decorate.c | 2 ++
t/t4217-log-limit.sh | 1 +
t/t5811-proto-disable-git.sh | 2 ++
t/t9004-example.sh | 2 ++
10 files changed, 74 insertions(+), 16 deletions(-)
-Peff
next reply other threads:[~2023-10-05 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 21:28 Jeff King [this message]
2023-10-05 21:29 ` [PATCH 1/3] decorate: add clear_decoration() function Jeff King
2023-10-05 21:30 ` [PATCH 2/3] revision: clear decoration structs during release_revisions() Jeff King
2023-10-05 23:00 ` Junio C Hamano
2023-10-06 0:51 ` Jeff King
2023-10-06 16:42 ` Junio C Hamano
2023-10-05 21:33 ` [PATCH 3/3] daemon: free listen_addr before returning Jeff King
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=20231005212802.GA982892@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.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 NNTP newsgroup(s).