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

Re: [PATCH 3/5] get_shallow_commits: Avoid memory leak if a commit has been reached already.

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 25, 2006, 18:49 UTC
Message-ID
<Pine.LNX.4.63.0611251947310.30004@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<ek9u4f$vmk$1@sea.gmane.org>
Hi,
On Sat, 25 Nov 2006, Anand Kumria wrote:
> Any reason you didn't do:
> 
> if (!commit->util)
> 	commit->util = xcalloc(1, sizeof(int));

xmalloc() does not initialize the memory. Therefore, it is usually preferred if you initialize the memory yourself. In this case, the memory is initialized to 0, even if it is not allocated.

It may be a minor performance issue, but it is a good habit to use xcalloc only if it is needed.

Ciao, Dscho

Previous: Anand KumriaNext: Junio C Hamano
Message 3 of 5 in “get_shallow_commits: Avoid memory leak if a commit has been reached already.”
  1. 3/5 get_shallow_commits: Avoid memory leak if a commit has been reached already.Alexandre Julliard, Nov 24, 2006
  2. Anand KumriaNov 25, 2006
  3. Johannes SchindelinNov 25, 2006
  4. Junio C HamanoNov 25, 2006
  5. Johannes SchindelinNov 25, 2006

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.