This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [PATCH] Let dwarf2 CFI's execute_stack_op be used outside ofCFI
- From: Petr Sorfa <petrs at caldera dot com>
- To: Daniel Berlin <dan at dberlin dot org>
- Cc: Jim Blandy <jimb at redhat dot com>, gdb-patches at sources dot redhat dot com
- Date: Tue, 02 Apr 2002 11:25:48 -0500
- Subject: Re: [PATCH] Let dwarf2 CFI's execute_stack_op be used outside ofCFI
- Organization: Caldera
- References: <Pine.LNX.4.44.0204020953001.4001-100000@dberlin.org>
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