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

Re: [PATCH] remote: plug memory leaks at early returns

From
René Scharfe <l.s.r@web.de>
Date
Aug 24, 2024, 08:06 UTC
Message-ID
<56522704-3023-44a7-ba01-7b0dea6b9bdf@web.de>
In-Reply-To
<xmqqseuvndsq.fsf@gitster.g>
Am 23.08.24 um 23:13 schrieb Junio C Hamano:
Show 8 quoted lines
> René Scharfe <l.s.r@web.de> writes:
>
>> Signed-off-by: René Scharfe <l.s.r@web.de>
>> ---
>>  builtin/remote.c | 23 +++++++++++++++--------
>>  1 file changed, 15 insertions(+), 8 deletions(-)
>
> Does this allow us to mark any test script as leak-free?

I don't think so -- at least GIT_TEST_PASSING_SANITIZE_LEAK=check still passes for me.

> Will queue in the meantime but may drop it if Patrick says it
> already is covered or something.
OK.
René
Previous: Junio C HamanoNext: Patrick Steinhardt
Message 3 of 5 in “remote: plug memory leaks at early returns”
  1. remote: plug memory leaks at early returnsRené Scharfe, Aug 23, 2024
  2. Junio C HamanoAug 23, 2024
  3. René ScharfeAug 24, 2024
  4. Patrick SteinhardtAug 26, 2024
  5. Junio C HamanoAug 26, 2024

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.