Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Walker <keith.walker@arm.com>
To: Michal Ludvig <mludvig@suse.cz>,
	GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Location list support
Date: Fri, 21 Feb 2003 17:47:00 -0000	[thread overview]
Message-ID: <4.3.2.7.2.20030221173257.02997f68@mhsun1.maidenhead.arm.com> (raw)
In-Reply-To: <3E560801.6080703@suse.cz>

Michal,

>The structure symbol itself is filled up with the first loclist entry 
>found for this symbol (ie with the values for the lowest PC where the 
>symbol is valid).

Just to point out that the DWARF2 specification does not require the 
entries in the location list to be specified in any specific order .... 
therefore you shouldn't assume that the first entry is for the lowest PC 
where the symbol is valid.



Not related to your changes .... but I thought I would point out the 
following issue once variables can be described using location lists:

A location list allows for overlapping address ranges, ie.  Where a 
variables can be found in more that one place at a specific PC.    Now for 
reading the variable's value this means that you can read from any of the 
specified locations.   However if you allow writing of the variable's value 
then the write should be performed to all the locations where the variable 
can currently be found.

Keith


  parent reply	other threads:[~2003-02-21 17:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-21 11:06 Michal Ludvig
2003-02-21 17:11 ` Daniel Jacobowitz
2003-02-21 23:09   ` Michal Ludvig
2003-02-21 17:47 ` Keith Walker [this message]
2003-02-21 18:02   ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2003-02-01  7:50 Michal Ludvig
2003-02-01 16:57 ` 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=4.3.2.7.2.20030221173257.02997f68@mhsun1.maidenhead.arm.com \
    --to=keith.walker@arm.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mludvig@suse.cz \
    /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