Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Limited DW_OP_piece support
Date: Thu, 22 May 2003 18:42:00 -0000	[thread overview]
Message-ID: <3ECD19FF.7060106@redhat.com> (raw)
In-Reply-To: <1030522183033.ZM30789@localhost.localdomain>

> On May 22,  1:53pm, Andrew Cagney wrote:
> 
> 
>> > The patch below adds limited DW_OP_piece support to dwarf2expr.c.  I
>> > will post a patch to rs6000-tdep.c which illustrates what a
>> > ``dwarf2_compose_register_pieces'' method should look like.
> 
>> 
>> I think GDB needs to just learn about location lists :-/
> 
> 
> It certainly should, but I fail to see how that relates to the
> addition of DW_OP_piece support to GDB's DWARF 2 location expression
> evaluator.  I think that what you meant to say is that GDB should
> fully (and generically) support arbitrary location expressions. 
> (Remember that the term "location list" is used to describe objects
> whose location changes during its lifetime.)

Yes, too many context sensative terms.  A list of sub-locations.

Given a ``struct value'', the [list of] sub-locations (pieces?) that 
describe how to find that values raw bytes.

Andrew


> BTW, I notice that I forgot the ChangeLog entries for my patch.  Here
> they are:
> 
> 	* dwarf2expr.c (execute_stack_op): Add limited DW_OP_piece support.
> 	* gdbarch.sh (dwarf2_compose_register_pieces): New method.
> 	* gdbarch.c, gdbarch.h: Regenerate.
> 
> Kevin
> 



  reply	other threads:[~2003-05-22 18:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 17:00 Kevin Buettner
2003-05-22 17:53 ` Andrew Cagney
2003-05-22 18:30   ` Kevin Buettner
2003-05-22 18:42     ` Andrew Cagney [this message]
2003-05-22 18:19 ` Daniel Jacobowitz
2003-05-22 21:21   ` Kevin Buettner
2003-05-22 21:29     ` Daniel Jacobowitz
2003-05-22 21:42       ` Kevin Buettner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ECD19FF.7060106@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox