From: Joel Brobecker <brobecker@adacore.com>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: Symbols/blocks questions
Date: Sat, 19 Sep 2009 17:02:00 -0000 [thread overview]
Message-ID: <20090919170155.GO7961@adacore.com> (raw)
In-Reply-To: <200909192041.14173.ghost@cs.msu.su>
> Then, it's probably likewise not true for any other random address
> in block. And then, the only reliable way to identify a block is via
> its address.
I think that's correct. We have routines IIRC that locate the innermost
block for a PC, or something like that, but I don't think we identify
blocks by their start address...
> What I'm trying to do is make -stack-list-variables output block
> together with a name of variable, and make -var-create accept
> some block specification. This, together, should all to display
^^^allow ?
> shadowed variables in frontend. Looks like 'block' should be
> the string rendition of the address of struct block :-/
Depending on the language, lexical blocks can be named, and it looks
like DWARF supports that, so I suppose you could you that. But blocks
can definitely be annonymous too, in which case the "string rendition"
might be a challenge...
--
Joel
next prev parent reply other threads:[~2009-09-19 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 11:52 Vladimir Prus
2009-09-19 14:34 ` Matt Rice
2009-09-19 16:34 ` Joel Brobecker
2009-09-19 16:41 ` Vladimir Prus
2009-09-19 17:02 ` Joel Brobecker [this message]
2009-09-19 18:35 ` Vladimir Prus
2009-09-20 15:52 ` Joel Brobecker
2009-09-20 20:30 ` Daniel Jacobowitz
2009-09-22 9:47 ` Jerome Guitton
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=20090919170155.GO7961@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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