From: Tom Tromey <tromey@redhat.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] DWARF expression evaluation vs. GDB address encoding problems
Date: Thu, 24 Jun 2010 17:06:00 -0000 [thread overview]
Message-ID: <m3tyos8inm.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201006232029.o5NKTrDf009422@d12av02.megacenter.de.ibm.com> (Ulrich Weigand's message of "Wed, 23 Jun 2010 22:29:53 +0200 (CEST)")
>>>>> "Ulrich" == Ulrich Weigand <uweigand@de.ibm.com> writes:
Ulrich> In fact, this seems the real problem to me: operations on the DWARF
Ulrich> stack should really use the target pointer / address representation;
Ulrich> only after the computation is complete should the value be converted
Ulrich> into the GDB internal address representation (CORE_ADDR).
This makes sense to me.
Ulrich> As a side effect, we no longer need to employ the value machinery
Ulrich> to perform binary operations on the DWARF stack.
Nice.
Ulrich> Tom, does this look reasonable to you?
Yes, thanks.
Tom
next prev parent reply other threads:[~2010-06-24 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 20:30 Ulrich Weigand
2010-06-24 17:06 ` Tom Tromey [this message]
2010-06-25 13:02 ` Ulrich Weigand
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=m3tyos8inm.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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