From: Daniel Jacobowitz <drow@mvista.com>
To: fnf@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: DW_OP_piece coming in gcc 3.4
Date: Fri, 06 Feb 2004 16:36:00 -0000 [thread overview]
Message-ID: <20040206163653.GA16536@nevyn.them.org> (raw)
In-Reply-To: <200402060930.34787.fnf@ninemoons.com>
On Fri, Feb 06, 2004 at 09:30:34AM -0700, Fred Fish wrote:
> I've been tasked with fixing this problem, or at least deciding if it
> can be fixed in the amount of time I have available to work on it.
Great!
> I've scanned most of the prior messages on the gdb@sources.redhat.com
> and gdb-patches@sources.redhat.com mailing lists which can be found by
> searching for DW_OP_piece. I intend to go back today and study them
> in detail to get some history on what has been discussed about this
> problem.
>
> If you have contributed to this topic in the past and have some new
> suggestions and/or ideas, or want to contribute, I'd appreciate any
> additional relevant input.
At this point, I believe the correct fix will be mostly contained to
the dwarf2-expr and dwarf2-loc code. A _complete_ fix will be quite
complicated; enough to print variables will not be too hard, since we
can read them in the LOC_COMPUTED read method, and mark them as
not_lval.
The problem I see with being able to write and fully use such variables
is that we need to audit uses of SYMBOL_VALUE_ADDRESS to find which are
used for full symbols.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-06 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 16:30 Fred Fish
2004-02-06 16:36 ` Daniel Jacobowitz [this message]
2004-02-16 19:25 ` Andrew Cagney
2004-02-16 19:42 ` Fred Fish
2004-02-17 7:39 ` Andreas Jaeger
2004-02-17 15:11 ` Daniel Jacobowitz
2004-02-18 6:42 ` Fred Fish
-- strict thread matches above, loose matches on Subject: below --
2004-01-30 5:27 Michael Elizabeth Chastain
2004-01-30 5:52 ` Kevin Buettner
2004-01-30 15:06 ` 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=20040206163653.GA16536@nevyn.them.org \
--to=drow@mvista.com \
--cc=fnf@redhat.com \
--cc=gdb@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