From: Joel Brobecker <brobecker@adacore.com>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: Symbols/blocks questions
Date: Sun, 20 Sep 2009 15:52:00 -0000 [thread overview]
Message-ID: <20090920155154.GS7961@adacore.com> (raw)
In-Reply-To: <200909192235.37739.ghost@cs.msu.su>
> Well, string rendition is not really a challenge. You take
> struct block *, and then use phex :-) The id need not be
> stable across debug sessions, it just should be stable within
> one debug session.
OK - I just thought that you wanted the user to be able to identify
these blocks from the source code. The same way we do when doing
(gdb) print FUNC::VAR
If you think people will be happy with an arbitrary block ID, then
indeed, that's easy (it's actually how task IDs are identified in
VxWorks, it's the address of the TCB).
--
Joel
next prev parent reply other threads:[~2009-09-20 15:52 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
2009-09-19 18:35 ` Vladimir Prus
2009-09-20 15:52 ` Joel Brobecker [this message]
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=20090920155154.GS7961@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