git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Cleaning up die() error messages
Date: Tue, 11 Oct 2005 21:40:37 -0700	[thread overview]
Message-ID: <434C93C5.9040505@zytor.com> (raw)
In-Reply-To: <7vd5mbqs2x.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:
> "H. Peter Anvin" <hpa@zytor.com> writes:
> 
>>I thought about this, and probably the sanest way is to wrap malloc() 
>>with something that creates a linked list of allocations.  If we abort, 
>>we can unwind the linked list and free all allocations.
> 
> You can free() the allocated memory with something like that,
> but it is likely that the aborted function would have already
> created some linked structure out of those memory blocks, and
> cleaning up that you would need the real exception handling
> wouldn't you?
> 

Not unless any of those linked structures can be reached from outside 
the git library.

	-hpa

  reply	other threads:[~2005-10-12  4:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-10 10:50 [RFC] Cleaning up die() error messages Elfyn McBratney
2005-10-10 19:04 ` Junio C Hamano
2005-10-11 19:48   ` Matthias Urlichs
2005-10-11 20:50     ` H. Peter Anvin
2005-10-12  1:20       ` Matthias Urlichs
2005-10-12  3:18         ` H. Peter Anvin
2005-10-12  4:25           ` Junio C Hamano
2005-10-12  4:40             ` H. Peter Anvin [this message]
2005-10-12  5:02               ` Junio C Hamano
2005-10-12  6:04           ` Matthias Urlichs
2005-10-10 20:14 ` Daniel Barkalow
2005-10-11 15:02 ` Alex Riesen
2005-10-11 16:11   ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=434C93C5.9040505@zytor.com \
    --to=hpa@zytor.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).