From: Stefan Beller <sbeller@google.com>
To: git@vger.kernel.org, gitster@pobox.com
Cc: Stefan Beller <sbeller@google.com>
Subject: [PATCH 4/6] wt-status.c: fix a memleak
Date: Fri, 27 Mar 2015 15:09:07 -0700 [thread overview]
Message-ID: <1427494150-8085-8-git-send-email-sbeller@google.com> (raw)
In-Reply-To: <1427494150-8085-1-git-send-email-sbeller@google.com>
In any code path of shorten_unambiguous_ref the return value is a
xstrdup(some string), so it is safe to free the variable `base`
in any codepath.
Signed-off-by: Stefan Beller <sbeller@google.com>
---
wt-status.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/wt-status.c b/wt-status.c
index 853419f..9d2a349 100644
--- a/wt-status.c
+++ b/wt-status.c
@@ -1576,6 +1576,8 @@ static void wt_shortstatus_print_tracking(struct wt_status *s)
color_fprintf(s->fp, header_color, "]");
fputc(s->null_termination ? '\0' : '\n', s->fp);
+
+ free((char *)base);
}
void wt_shortstatus_print(struct wt_status *s)
--
2.3.0.81.gc37f363
next prev parent reply other threads:[~2015-03-27 22:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 22:09 [PATCH 0/6] Memory leaks once again Stefan Beller
2015-03-27 22:09 ` [PATCH 1/6] pack-bitmap: fix a memleak Stefan Beller
2015-03-27 22:09 ` [PATCH 1/6] shallow: " Stefan Beller
2015-03-27 22:09 ` [PATCH 2/6] line-log.c: " Stefan Beller
2015-03-27 22:09 ` [PATCH 2/6] shallow: " Stefan Beller
2015-03-27 22:09 ` [PATCH 3/6] line-log.c: " Stefan Beller
2015-03-27 22:09 ` [PATCH 4/6] " Stefan Beller
2015-03-27 22:09 ` Stefan Beller [this message]
2015-03-27 22:09 ` [PATCH 5/6] pack-bitmap: " Stefan Beller
2015-03-27 22:09 ` [PATCH 5/6] wt-status.c: " Stefan Beller
2015-03-27 22:09 ` [PATCH 6/6] WIP/RFC/entry.c: " Stefan Beller
2015-03-27 22:12 ` [PATCH 0/6] Memory leaks once again Stefan Beller
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=1427494150-8085-8-git-send-email-sbeller@google.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 NNTP newsgroup(s).