From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10935 invoked by alias); 6 Apr 2002 05:31: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 10927 invoked from network); 6 Apr 2002 05:31:51 -0000 Received: from unknown (HELO dberlin.org) (64.246.6.106) by sources.redhat.com with SMTP; 6 Apr 2002 05:31:51 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by dberlin.org (8.11.6/8.11.6) with ESMTP id g365Vom25032; Sat, 6 Apr 2002 00:31:50 -0500 Date: Fri, 05 Apr 2002 21:31:00 -0000 From: Daniel Berlin To: Jim Blandy cc: gdb@sources.redhat.com Subject: Re: Getting rid of the symbol_ranges and aliases stuff In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-04/txt/msg00074.txt.bz2 On 5 Apr 2002, Jim Blandy wrote: > > Daniel Berlin writes: > > This is the live range splitting extensions to stabs stuff. It works by > > having multiple symbols that are aliases to a given symbol at a given PC. > > In effect, it uses multiple symbols to simulate DWARF2 location lists. > > It could be reimplemented in terms of location functions, cleanly. > > > > But since nothing publicly available generates the info, I can't do that > > as part of a LOC_COMPUTED and LOC_COMPUTED_ARG implementation. > > Nor do I think I should be required to. > > You should just ignore the old LRS stuff. The Dwarf 2 location lists > should be single symbols with the LOC_COMPUTED address class with a > `read_variable' method which use the PC from the frame it recieves to > choose the right location expression. > Yes, I know. > I guess I don't see how the old LRS stuff is in your way. Um, if I remove everything but LOC_COMPUTED and LOC_COMPUTED_ARG, and replace them with sets of functions, it means the live range stuff needs to be dealt with. It's not in the way for the first patch (which just adds LOC_COMPUTED and LOC_COMPUTED_ARG), but it'll be in the way soon after, as things are converted to use them. If you look, I said I can't convert them as part of replacing the existing classes with LOC_COMPUTED and LOC_COMPUTED_ARG, and i don't think i should be required to. >From a practical perspective would be easier to remove them now, than remove them as part of a followup patch to the LOC_COMPUTED introduction that does the conversion (which is when they'd be in the way). It's cleaner.