From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20301 invoked by alias); 10 Aug 2004 15:51:51 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 20294 invoked from network); 10 Aug 2004 15:51:51 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 10 Aug 2004 15:51:51 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i7AFpoe3026031 for ; Tue, 10 Aug 2004 11:51:50 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i7AFpoa22890; Tue, 10 Aug 2004 11:51:50 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 033342B9D; Tue, 10 Aug 2004 11:51:43 -0400 (EDT) Message-ID: <4118EF0F.9000502@gnu.org> Date: Tue, 10 Aug 2004 15:51:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040801 MIME-Version: 1.0 To: Andrew Cagney , Nathanael Nerode Cc: gdb@sources.redhat.com Subject: Re: Removing leftover traces of mmalloc? References: <20040805210710.GA15265@twcny.rr.com> <41139C3D.3080502@gnu.org> In-Reply-To: <41139C3D.3080502@gnu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00150.txt.bz2 >> With the removal of mmalloc support from gdb, nothing in src or gcc is >> actually using mmalloc. Furthermore, support appears to have been removed >> prior to the branching of GDB 6.1. >> >> Would it be appropriate to delete the mmalloc directory and all the trailing >> references thereto? If not, would it at any rate be appropriate to stop >> shipping it with GDB and delete the various trailing references? > > > I think it is fine to break the the GDB <-> mmalloc connection (by zapping it from config et.al.). Hmm, I just noted some lingering calls to [x]mmalloc in the objfile reader. I'll replace them (their reason for being there is gone). Since GDB works around the lack of mmalloc this wouldn't have been noticed. Andrew > As for removing it (cvs rm -f), perhaphs we can avoid it (although I don't care). > > GDB has a growing list of top-level src directories that it doesn't need to be included in a distro (src/mmalloc/ is one). I think its time to prune the `gdb' module (which, I know, is not a very backward compatible thing to do). > > Andrew > > PS: But `what-if' GDB needs to replace obstacks with something more like mmalloc (ah, the irony)? We can then revive it - here we need to deal with `what-is' :-)