From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7870 invoked by alias); 29 Apr 2003 16:24:54 -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 7802 invoked from network); 29 Apr 2003 16:24:31 -0000 Received: from unknown (HELO mhsun1.maidenhead.arm.com) (193.131.176.54) by sources.redhat.com with SMTP; 29 Apr 2003 16:24:31 -0000 Received: from mhpc6.arm.com (mhpc6 [192.168.2.53]) by mhsun1.maidenhead.arm.com (8.9.3/8.9.3) with ESMTP id RAA12923; Tue, 29 Apr 2003 17:16:29 +0100 (BST) Message-Id: <4.3.2.7.2.20030429170707.02ac6180@mhsun1.maidenhead.arm.com> X-Sender: kwalker@mhsun1.maidenhead.arm.com Date: Tue, 29 Apr 2003 16:24:00 -0000 To: Daniel Berlin From: Keith Walker Subject: Re: macros, debug information, and parse_macro_definition Cc: gdb@sources.redhat.com In-Reply-To: References: <3EAE927E.4030005@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-SW-Source: 2003-04/txt/msg00328.txt.bz2 At 11:55 29/04/2003 -0400, Daniel Berlin wrote: >It's trivial to do macro information compression, unlike normal dwarf2 >info compression, because the macro info has no references. It is what it >is. With a smart algorithm (it's a bit tricky to keep the semantics the >same after merging all the macro infos), you could simply take all the >macro infos, merge them, make one macro info, and point all the debug >sections at it. >I think, anyway. I'm not sure whether your comment is about macro info in general or about macro info in DWARF2. Unfortunately, for DWARF2 debugging information, I don't think it is quite so easy in that the macro information can include file start/end entries which refer to file entries in the associated line number information - so you would also have to do something about merging the line number tables as well; and hence update all other entries that refer to the file entries. Keith