[PATCH 26/29] line-range: plug leaking find functions

From: Patrick Steinhardt <ps@pks.im>
Date: Jun 3, 2024, 09:48 UTC
Message-ID: <ba9c2b4ea73be5e9c2529921b6491b9baaf661d5.1717402439.git.ps@pks.im>
In-Reply-To: <cover.1717402439.git.ps@pks.im>

In `parse_range_funcname()` we may end up allocating a "find function", but never free it. Fix this.

Signed-off-by: Patrick Steinhardt <ps@pks.im>
---
 line-range.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/line-range.c b/line-range.c
index 60f0e5ada8..b99f0d9895 100644
--- a/line-range.c
+++ b/line-range.c
@@ -234,6 +234,8 @@ static const char *parse_range_funcname(
 	}
 
 	regfree(&regexp);
+	if (xecfg)
+		xdiff_clear_find_func(xecfg);
 	free(xecfg);
 	free(pattern);

-- 
2.45.1.410.g58bac47f8e.dirty

$ 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.