Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa/6.0] Fix a thinko in dwarf2loc
Date: Thu, 11 Sep 2003 17:17:00 -0000	[thread overview]
Message-ID: <20030911171708.GA8447@nevyn.them.org> (raw)
In-Reply-To: <16224.45033.39860.763199@localhost.redhat.com>

On Thu, Sep 11, 2003 at 01:24:57PM -0400, Elena Zannoni wrote:
> Daniel Jacobowitz writes:
>  > On Tue, Sep 09, 2003 at 06:59:52PM -0400, Andrew Cagney wrote:
>  > > > > >  > > > > +  return baton.needs_frame || ctx->in_reg;
>  > > > > >  > > > >  }
>  > > > > >  > > > >  
>  > > > > > 
>  > > > > > Hmmm, the ctx just got freed, you cannot dereference it. Need to use a
>  > > > > 
>  > > > > Eek, I'm embarassed.  You are so right.
>  > > > > 
>  > > > > > local variable.  What you are really saying here is that the
>  > > > > > needs_frame variable is not sufficient to describe what's needed. Can
>  > > > > > the case be added, so that needs_frame becomes OK? Proabably you
>  > > > > > need another need_frame_* function.
>  > > > > 
>  > > > > No, I can't.  The needs_frame_* functions are hooks for things which
>  > > > > are external to the expression evaluator - concepts like "object" and
>  > > > > "thread local storage address" which require information.  But the
>  > > > > evaluator won't actually try to read from the register when parsing a
>  > > > > DW_OP_reg1; it just sets in_reg.
>  > > >
>  > > >Oh, ok, I guess save ctx->in_reg in a local variable then.
>  > > >
>  > > >elena
>  > > 
>  > > Thanks for picking this up.  So there's no confusion I'm also ok with 
>  > > this on the branch.
>  > 
>  > Thank you both.  Checked in.
> 
> Just for completeness, can you post the patch?
> 
> thanks
> elena

Oops.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

2003-09-11  Daniel Jacobowitz  <drow@mvista.com>

	* dwarf2loc.c (dwarf2_loc_desc_needs_frame): Variables in a
	register do need a frame.

Index: dwarf2loc.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2loc.c,v
retrieving revision 1.12
diff -u -p -r1.12 dwarf2loc.c
--- dwarf2loc.c	22 Jul 2003 18:24:42 -0000	1.12
+++ dwarf2loc.c	11 Sep 2003 14:57:16 -0000
@@ -304,6 +304,7 @@ dwarf2_loc_desc_needs_frame (unsigned ch
 {
   struct needs_frame_baton baton;
   struct dwarf_expr_context *ctx;
+  int in_reg;
 
   baton.needs_frame = 0;
 
@@ -316,9 +317,11 @@ dwarf2_loc_desc_needs_frame (unsigned ch
 
   dwarf_expr_eval (ctx, data, size);
 
+  in_reg = ctx->in_reg;
+
   free_dwarf_expr_context (ctx);
 
-  return baton.needs_frame;
+  return baton.needs_frame || in_reg;
 }
 
 static void


      reply	other threads:[~2003-09-11 17:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 19:32 Daniel Jacobowitz
2003-08-17 20:58 ` Daniel Jacobowitz
2003-08-24 16:48   ` Daniel Jacobowitz
2003-09-07  4:12     ` Daniel Jacobowitz
2003-09-09 21:18       ` Elena Zannoni
2003-09-09 21:25         ` Daniel Jacobowitz
2003-09-09 22:45           ` Elena Zannoni
2003-09-09 22:59             ` Andrew Cagney
2003-09-11 15:50               ` Daniel Jacobowitz
2003-09-11 17:16                 ` Elena Zannoni
2003-09-11 17:17                   ` Daniel Jacobowitz [this message]

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=20030911171708.GA8447@nevyn.them.org \
    --to=drow@mvista.com \
    --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