git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 06/17] transport.c::get_refs_via_curl(): do not leak refs_url

From
Tay Ray Chuan <rctay89@gmail.com>
Date
May 29, 2009, 17:59 UTC
Message-ID
<20090530015903.96c4a18f.rctay89@gmail.com>
From:	Mike Hommey <mh@glandium.org>
Subject: [WIP Patch 02/12] Some cleanup in get_refs_via_curl()
Date:	Sun, 18 Jan 2009 09:04:27 +0100
Signed-off-by: Mike Hommey <mh@glandium.org>
Signed-off-by: Tay Ray Chuan <rctay89@gmail.com>
---
 transport.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/transport.c b/transport.c
index 17891d5..0aa57bd 100644
--- a/transport.c
+++ b/transport.c
@@ -519,6 +519,7 @@ static struct ref *get_refs_via_curl(struct transport *transport, int for_push)
 		free(ref);
 	}

+	free(refs_url);
 	return refs;
 }

--
1.6.3.1
Message 1 of 1 in “transport.c::get_refs_via_curl(): do not leak refs_url”
  1. 06/17 transport.c::get_refs_via_curl(): do not leak refs_urlTay Ray Chuan, May 29, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.