Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: LOC_COMPUTED + abstracted dwarf2 evaluator, again
Date: Tue, 09 Jul 2002 14:03:00 -0000	[thread overview]
Message-ID: <np3cus4nwt.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207081254320.23006-100000@dberlin.org>


Daniel Berlin <dberlin@dberlin.org> writes:
> + /* Evaluate a location description, given in THEBLOCK, in the
> +    context of frame FRAME. */
> + static struct value *
> + evaluate_loc_desc (struct symbol *var, struct frame_info *frame,
> + 		   struct dwarf_block *theblock, struct type *type)
> + {
> +   CORE_ADDR result;
> +   struct value * retval;
> +   struct dwarf_expr_baton *baton = xmalloc (sizeof (struct dwarf_expr_baton));
> +   struct dwarf_expr_context *ctx;
> +   
> +   retval = allocate_value(type);
> +   baton->var = var;
> +   baton->frame = frame;
> +   
> +   VALUE_LVAL (retval) = lval_memory;
> +   VALUE_BFD_SECTION (retval) = SYMBOL_BFD_SECTION (var);
> +   
> +   ctx = new_dwarf_expr_context ();
> +   ctx->read_reg_baton = baton;
> +   ctx->read_reg = dwarf_expr_read_reg;
> +   ctx->read_mem_baton = baton;
> +   ctx->read_mem = dwarf_expr_read_mem;
> +   ctx->get_frame_base_baton = baton;
> +   ctx->get_frame_base = dwarf_expr_frame_base;
> +   ctx->error = error;
> +   
> +   dwarf_expr_eval (ctx, theblock->data, theblock->size);
> +   
> +   if (ctx->in_reg)
> +     {
> +       store_typed_address (VALUE_CONTENTS_RAW (retval), 
> + 			   SYMBOL_TYPE (var), dwarf_expr_fetch (ctx, 0));
> +       VALUE_LVAL (retval) = not_lval;
> +     }
> +   else
> +     {
> +       result = dwarf_expr_fetch (ctx, 0);
> +       VALUE_LAZY (retval) = 1;
> +       VALUE_ADDRESS (retval) = result;
> +     }

This looks wrong.  If evaluating the Dwarf location expression yields
an `in_reg' result, shouldn't the value be an lval_register, with its
the address set to the register number?

I think the evaluator is confused in this regard, too; see my upcoming
post about that.


  parent reply	other threads:[~2002-07-09 21:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08 11:02 Daniel Berlin
2002-07-08 14:30 ` Jim Blandy
2002-07-08 16:44   ` Daniel Berlin
2002-07-08 19:03     ` Jim Blandy
2002-07-09 14:03 ` Jim Blandy [this message]
2002-07-09 14:08   ` Daniel Berlin
2002-07-09 15:47     ` Jim Blandy
2002-07-09 16:00       ` Daniel Berlin
2003-01-30 23:59 ` Daniel Jacobowitz

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=np3cus4nwt.fsf@zwingli.cygnus.com \
    --to=jimb@redhat.com \
    --cc=dberlin@dberlin.org \
    --cc=gdb-patches@sources.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