From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30667 invoked by alias); 22 Jun 2003 21:42:10 -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 30488 invoked from network); 22 Jun 2003 21:42:05 -0000 Received: from unknown (HELO localhost.redhat.com) (24.157.166.107) by sources.redhat.com with SMTP; 22 Jun 2003 21:42:05 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 3A43C2B5F for ; Sun, 22 Jun 2003 17:41:59 -0400 (EDT) Message-ID: <3EF622A7.70005@redhat.com> Date: Sun, 22 Jun 2003 21:42:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: gdbarch as an obstack Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-06/txt/msg00436.txt.bz2 Hello, I'm thinking of changing the gdbarch memory allocator to an obstack. The intent being to greatly simplify the memory management code that goes with a gdbarch object. At present there are these callups but they can just go! Andrew