Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: <gdb@sourceware.org>
Subject: Re: Complex DWARF expressions
Date: Mon, 22 Sep 2014 06:03:00 -0000	[thread overview]
Message-ID: <87a95sxkjr.fsf@codesourcery.com> (raw)
In-Reply-To: <83sijkydk4.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 21 Sep	2014 22:32:43 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>     Range 0x100aaf7-0x100ad4c: a complex DWARF expression:
>        0: DW_OP_GNU_entry_value
> 	 2: DW_OP_reg2 [$edx]
>        3: DW_OP_stack_value
>
> "A variable in $edx" I understand, but what about the "complex DWARF
> expression" parts?  Is there any way a mere mortal such as myself can
> decipher this to the effect of understanding in which register or at
> what address can I look up the value, assuming that I know at which PC
> address the program stopped?
>
> (Yes, I've looked at the DWARF Standard, but couldn't understand from
> the description of these location descriptors how to convert them to
> either a register or a memory address.)

DW_OP_GNU_entry_value isn't in DWARF Standard and it is documented here
http://www.dwarfstd.org/ShowIssue.php?issue=100909.1

If I understand the doc above correctly, the entry above means if PC is
within range 0x100aaf7-0x100ad4c, the value of new_width is the value of
$edx at the moment entering this function.  IOW, to get value of
new_width, needs to unwind frame and read $edx.

-- 
Yao (齐尧)


  reply	other threads:[~2014-09-22  6:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-21 19:33 Eli Zaretskii
2014-09-22  6:03 ` Yao Qi [this message]
2014-09-22  6:17   ` Jan Kratochvil
2014-09-22 18:21     ` Eli Zaretskii
2014-09-22 18:44       ` Jan Kratochvil
2014-09-22 19:06         ` Eli Zaretskii
2014-09-22 19:21           ` Jan Kratochvil

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=87a95sxkjr.fsf@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.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