Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Berlin <dberlin@redhat.com>
Cc: David Taylor <taylor@candd.org>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Add support for tracking/evaluating dwarf2 location  expressions
Date: Fri, 06 Apr 2001 12:02:00 -0000	[thread overview]
Message-ID: <3ACE12CA.E6176DDD@cygnus.com> (raw)
In-Reply-To: <m27l168xk7.fsf@dynamic-addr-83-177.resnet.rochester.edu>

Daniel Berlin wrote:
> 
> Andrew Cagney <ac131313@cygnus.com> writes:
> 
> > > So the code doesn't belong in dwarf2read.c.  dwarf2read.c is a symbol
> > > reader. dwarf2 location expressions are a way of describing variable
> > > locations.  The other code to process the current gdb address
> > > classes/locations is in findvar.c, so that's where i put it.
> >
> > No.
> >
> >     if (frame == NULL)
> >       frame = selected_frame;
> > !   if (SYMBOL_DWARF2_LOC (var) != NULL)
> > !     return evaluate_dwarf2_locdesc (var, frame, (struct dwarf_block *)

Some code, somewhere must be setting SYMBOL_DWARF2_LOC (var).  At a
guess that code is either in dwarf2read.c or in a file using information
obtained from dwarf2read.c.  

If SYMBOL_DWARF2_LOC() was replaced by a more generic method then, I'd
expect that method to live in dwarf2read.c since it would be
dwarf2read.c creating a type that contained that method.

> > For this starts to make sense, I suspect it needs to be given some
> > additional context - namely where in dwarf2read.c things are also going
> > to be changed.
> 
> Make sense?
> In what way?

It might help explain how this patch ties in to the rest of GDB.

	enjoy,
		Andrew


  reply	other threads:[~2001-04-06 12:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-30 13:49 David Taylor
2001-03-30 14:42 ` Daniel Berlin
2001-03-30 15:14   ` Andrew Cagney
2001-03-30 18:44     ` Daniel Berlin
2001-03-30 15:23   ` Elena Zannoni
2001-03-30 15:24   ` Andrew Cagney
2001-03-30 18:46     ` Daniel Berlin
2001-04-06 12:02       ` Andrew Cagney [this message]
2001-04-06 12:40         ` Daniel Berlin
  -- strict thread matches above, loose matches on Subject: below --
2001-03-30 11:11 Daniel Berlin
2001-03-30 15:36 ` Andrew Cagney
2001-03-30 18:53   ` Daniel Berlin
2001-04-06 11:53     ` Andrew Cagney
2001-04-06 12:10       ` Daniel Berlin
2001-04-06 12:36         ` Kevin Buettner
2001-05-21 14:46 ` Jim Blandy
2001-05-21 18:49   ` Daniel Berlin
2001-05-22 12:46     ` Jim Blandy
2001-05-22 13:51       ` Daniel Berlin
2001-05-22 23:14         ` Jim Blandy
2001-05-23  8:51           ` Daniel Berlin
2001-05-23 11:53           ` Daniel Berlin
2001-05-23 21:53             ` Jim Blandy
2001-05-23 22:56               ` Daniel Berlin
2001-06-06  9:07   ` Andrew Cagney
2001-06-06  9:46     ` Daniel Berlin
2001-06-07  7:29       ` Andrew Cagney

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=3ACE12CA.E6176DDD@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=dberlin@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=taylor@candd.org \
    /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