From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5430 invoked by alias); 2 Apr 2002 16:19:04 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 5419 invoked from network); 2 Apr 2002 16:19:03 -0000 Received: from unknown (HELO tetsuo.nj.caldera.com) (63.124.204.226) by sources.redhat.com with SMTP; 2 Apr 2002 16:19:03 -0000 Received: from caldera.com (localhost.localdomain [127.0.0.1]) by tetsuo.nj.caldera.com (8.11.6/8.11.6) with ESMTP id g32GPq932101; Tue, 2 Apr 2002 11:25:53 -0500 Message-ID: <3CA9DB8C.4A16D2A8@caldera.com> Date: Tue, 02 Apr 2002 08:19:00 -0000 From: Petr Sorfa Organization: Caldera X-Accept-Language: en MIME-Version: 1.0 To: Daniel Berlin CC: Jim Blandy , gdb-patches@sources.redhat.com Subject: Re: [PATCH] Let dwarf2 CFI's execute_stack_op be used outside ofCFI References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg00023.txt.bz2 Hi Dan, > > I've implemented a dwarf3 location expression parser for GDB. My > > solution is, well, different than yours. I've gone for a more simpler > > (limited) solution based on the existing dwarf2read.c decode_locdesc > > function. It basically processes the location expression data passed to > > through a "dwarf block" which contains the raw DWARF data block and it's > > size. > > I'm curious why you reimplemented this approach. > If you look back to last year, you'll note I sent something that does > exactly this, to gdb-patches. > I never got around to attach dwarf blocks to types, because Andrew wanted > it more independent of DWARF2. > You probably could have saved a lot of time in writing his stuff, which is > why i'm curious. As far as I recall your patch did not support Dwarf3 DW_OPs which were/are my more immediate concern. The main reason I did implement it was to get it done as quickly as possible. At the time we were still debating on the proper solution (before deciding on the independent approach - I am aware that a patch was made available supporting some of this last year.) Basically it is/was a proof of concept. It works. I also got the impression that other folks were working on the intermediate solution. If this is not the case I will gladly help implement relevant bits. Petr