From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [RFC] Cleaning up die() error messages Date: Tue, 11 Oct 2005 20:18:45 -0700 Message-ID: <434C8095.4080201@zytor.com> References: <20051010105008.GB30202@gentoo.org> <7vzmph42j2.fsf@assigned-by-dhcp.cox.net> <434C2590.3040107@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: git@vger.kernel.org X-From: git-owner@vger.kernel.org Wed Oct 12 05:20:44 2005 Return-path: Received: from vger.kernel.org ([209.132.176.167]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EPX9u-0004ZI-0X for gcvg-git@gmane.org; Wed, 12 Oct 2005 05:20:02 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932387AbVJLDT1 (ORCPT ); Tue, 11 Oct 2005 23:19:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932392AbVJLDT1 (ORCPT ); Tue, 11 Oct 2005 23:19:27 -0400 Received: from terminus.zytor.com ([192.83.249.54]:45253 "EHLO terminus.zytor.com") by vger.kernel.org with ESMTP id S932387AbVJLDT0 (ORCPT ); Tue, 11 Oct 2005 23:19:26 -0400 Received: from [172.27.0.18] (c-67-180-238-27.hsd1.ca.comcast.net [67.180.238.27]) (authenticated bits=0) by terminus.zytor.com (8.13.4/8.13.4) with ESMTP id j9C3IjtK009088 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Oct 2005 20:18:46 -0700 User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) X-Accept-Language: en-us, en To: Matthias Urlichs In-Reply-To: X-Virus-Scanned: ClamAV version 0.87, clamav-milter version 0.87 on localhost X-Virus-Status: Clean X-Spam-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_00, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on terminus.zytor.com Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: Matthias Urlichs wrote: > > I thought about doing something like that, but ... >>However, a much bigger problem is cleanup. > > ... exactly. > 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. -hpa