Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: container_of equivalent in gdb-python script
Date: Wed, 10 Jun 2009 22:13:00 -0000	[thread overview]
Message-ID: <4A302FEB.1060509@web.de> (raw)
In-Reply-To: <m33aa7g40e.fsf@fleche.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

Tom Tromey wrote:
>>>>>> "Jan" == Jan Kiszka <jan.kiszka@web.de> writes:
> 
> Daniel> It's typical to do this the same way folks do in C: Create a null
> Daniel> pointer of the right type.
> 
> Jan> You can't do that with the current upstream python interface, but the
> Jan> parse_and_eval solves this nicely.
> 
> Actually, for constants you can:
> 
> (gdb) python print gdb.Value(0)
> 0
> (gdb) python print type(gdb.Value(0))
> <type 'gdb.Value'>
> (gdb) python print gdb.Value(0).cast(gdb.lookup_type('char').pointer())
> 0x0

Yeah, seen this (in the testsuite). But such objects neither have
addresses, nor do they help with non-constant objects I'm interested in.

> 
> Whoops, this seems to be undocumented.

Not the only piece... :)

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2009-06-10 22:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 16:56 Jan Kiszka
2009-06-10 18:57 ` Tom Tromey
2009-06-10 20:10   ` Jan Kiszka
2009-06-10 20:37     ` Tom Tromey
2009-06-10 21:06       ` Jan Kiszka
2009-06-10 20:42     ` Daniel Jacobowitz
2009-06-10 21:33       ` Jan Kiszka
2009-06-10 21:42         ` Tom Tromey
2009-06-10 22:13           ` Jan Kiszka [this message]
2009-06-10 22:17             ` Tom Tromey
2009-06-11  9:51               ` Jan Kiszka

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=4A302FEB.1060509@web.de \
    --to=jan.kiszka@web.de \
    --cc=gdb@sourceware.org \
    --cc=tromey@redhat.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