From binutils-return-16865-listarch-binutils=sourceware dot cygnus dot com at sources dot redhat dot com Thu Apr 04 00:09:44 2002 Return-Path: Delivered-To: listarch-binutils at sourceware dot cygnus dot com Received: (qmail 22882 invoked by alias); 4 Apr 2002 00:09:43 -0000 Mailing-List: contact binutils-help at sources dot redhat dot com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner at sources dot redhat dot com Delivered-To: mailing list binutils at sources dot redhat dot com Received: (qmail 22874 invoked from network); 4 Apr 2002 00:09:41 -0000 Received: from unknown (HELO mta06bw.bigpond.com) (139.134.6.96) by sources dot redhat dot com with SMTP; 4 Apr 2002 00:09:41 -0000 Received: from bubble.local ([144.135.24.87]) by mta06bw dot bigpond dot com (Netscape Messaging Server 4 dot 15 mta06bw Feb 26 2002 03:44:21) with SMTP id GU0OG300 dot 5A9 for ; Thu, 4 Apr 2002 10:09:39 +1000 Received: from CPE-144-136-176-14.sa.bigpond.net.au ([144.136.176.14]) by bwmam07.mailsvc.email.bigpond.com(MailRouter V3.0i 62/99867); 04 Apr 2002 10:09:39 Received: (qmail 25963 invoked by uid 179); 4 Apr 2002 00:09:39 -0000 Date: Thu, 4 Apr 2002 09:39:39 +0930 From: Alan Modra To: binutils at sources dot redhat dot com Subject: Re: Two memory management questions in BFD - link hash tables Message-ID: <20020404000939.GL1042@bubble.sa.bigpond.net.au> Mail-Followup-To: binutils at sources dot redhat dot com References: <20020330230234.A14860@nevyn.them.org> <20020403142929.GJ1042@bubble.sa.bigpond.net.au> <20020403181054.A842@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020403181054 dot A842 at nevyn dot them dot org> User-Agent: Mutt/1.3.25i On Wed, Apr 03, 2002 at 06:10:54PM -0500, Daniel Jacobowitz wrote: > > It adds bfd_link_hash_table_free (abfd, hash), and changes to > malloc'ing the hashes. I can absolutely guarantee that it leaks memory > on some platforms; any time we notice one, we can fix it. > best I can do, since figuring out where these things are allocated is > insanely frustrating... ldlang.c:open_output The patch looks OK to me. -- Alan Modra IBM OzLabs - Linux Technology Centre