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

Re: [PATCH 01/11] Fix memory leak in traverse_commit_list

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 9, 2007, 23:51 UTC
Message-ID
<Pine.LNX.4.64.0711092350440.4362@racer.site>
In-Reply-To
<7vmytnqbu2.fsf@gitster.siamese.dyndns.org>
Hi,
On Fri, 9 Nov 2007, Junio C Hamano wrote:
Show 16 quoted lines
> "Shawn O. Pearce" <spearce@spearce.org> writes:
> 
> > diff --git a/list-objects.c b/list-objects.c
> > index e5c88c2..713bef9 100644
> > --- a/list-objects.c
> > +++ b/list-objects.c
> > @@ -170,4 +170,11 @@ void traverse_commit_list(struct rev_info *revs,
> >  	}
> >  	for (i = 0; i < objects.nr; i++)
> >  		show_object(&objects.objects[i]);
> > +	free(objects.objects);
> > +	if (revs->pending.nr) {
> > +		revs->pending.nr = 0;
> > +		revs->pending.alloc = 0;
> > +		revs->pending.objects = NULL;
> > +		free(revs->pending.objects);

Umm. Isn't this the wrong way around? Should you not free() first, and then set to NULL?

Ciao, Dscho

Previous: Junio C HamanoNext: Shawn O. Pearce
Message 3 of 4 in “Fix memory leak in traverse_commit_list”
  1. 01/11 Fix memory leak in traverse_commit_listShawn O. Pearce, Nov 9, 2007
  2. Junio C HamanoNov 9, 2007
  3. Johannes SchindelinNov 9, 2007
  4. Shawn O. PearceNov 11, 2007

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.