From: "André Pönitz" <andre.poenitz@nokia.com>
To: gdb@sourceware.org
Subject: Re: Python API questions and use cases
Date: Thu, 16 Sep 2010 09:57:00 -0000 [thread overview]
Message-ID: <201009161154.02756.andre.poenitz@nokia.com> (raw)
In-Reply-To: <4C91E3AE.6070500@wh2.tu-dresden.de>
On Thursday 16 September 2010 11:30:22 ext Joachim Protze wrote:
> Am 16.09.2010 09:32, schrieb Joel Borggrén-Franck:
> > On Wed, Sep 15, 2010 at 7:56 PM, Tom Tromey <tromey@redhat.com> wrote:
> >> I think the tricky part is getting a Value holding the appropriate
> >> constant. For that you might not have anything better, at present, than
> >> parse_and_eval.
> >
> > True. Then I think this would be useful:
> >
> > gdb.new_address(addr) - returns a new gdb.Value (of type (void *)) pointing
> > to addr. addr is checked to be within bounds of the address space of the
> > inferior upon creation.
> >
>
> Where do you get this address from? I cannot imagine a case where you
> get a valid address from others than from inferior. So you have the
> address as gdb.Value already.
There are lots of cases where the address is not in a gdb.Value already.
The address may come from the inferior, but not through Python, e.g
by parsing some CLI output. Or the address might be the result of some
manual computation. Or the address is some fixed value also known
on the outside.
Andre'
next prev parent reply other threads:[~2010-09-16 9:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 13:43 Joel Borggrén-Franck
2010-09-15 18:01 ` Tom Tromey
2010-09-15 19:04 ` Phil Muldoon
2010-09-16 6:13 ` Joel Borggrén-Franck
2010-09-16 7:33 ` Joel Borggrén-Franck
2010-09-16 9:30 ` Joachim Protze
2010-09-16 9:57 ` André Pönitz [this message]
2010-09-16 9:49 ` André Pönitz
2010-09-16 11:56 ` Joel Borggrén-Franck
2010-09-16 19:11 ` Tom Tromey
2010-09-17 7:35 ` Joel Borggrén-Franck
2010-09-21 18:02 ` Tom Tromey
2010-09-16 19:09 ` Tom Tromey
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=201009161154.02756.andre.poenitz@nokia.com \
--to=andre.poenitz@nokia.com \
--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