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

Re: [PATCH] Fix handle leak in write_tree

From
Junio C Hamano <junkio@cox.net>
Date
Apr 24, 2007, 09:33 UTC
Message-ID
<7vps5u86bn.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<81b0412b0704240230x3a5b473k5da3d45d9c997c3b@mail.gmail.com>
"Alex Riesen" <raa.lkml@gmail.com> writes:
> ... Isn't such kind of resource control _generally_ nicer to implement
> in the top levels of a program?

In theory perhaps, but my understanding of our use of atexit() is to clean them up in situations beyond the control of the top levels of a program, most notably upon exit on signal.

Previous: Alex RiesenNext: Alex Riesen
Message 4 of 7 in “Fix handle leak in write_tree”
  1. Fix handle leak in write_treeAlex Riesen, Apr 23, 2007
  2. Junio C HamanoApr 24, 2007
  3. Alex RiesenApr 24, 2007
  4. Junio C HamanoApr 24, 2007
  5. Alex RiesenApr 25, 2007
  6. Junio C HamanoApr 25, 2007
  7. Fix handle leak in write_treeAlex Riesen, Apr 25, 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.