From: Tom Tromey <tromey@redhat.com>
To: pmuldoon@redhat.com
Cc: Christoph Mathys <eraserix@gmail.com>, gdb@sourceware.org
Subject: Re: passing gdb.Value pointers to ctypes function calls
Date: Wed, 13 Apr 2011 14:27:00 -0000 [thread overview]
Message-ID: <m31v162pms.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3aafv8909.fsf@redhat.com> (Phil Muldoon's message of "Tue, 12 Apr 2011 22:17:26 +0100")
>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:
>> I'm trying to write a pretty printer for gdb 7.2 using python, to be
>> concrete I would like to print an Xml node (libxml2) as text. I've
>> managed to get the pointers to node and document. Now I'm trying to
>> call libxml using ctypes module, passing the pointer values as
>> c_void_p. But gdb keeps crashing on me.
Phil> If GDB ever crashes it is a bug. Can you file a bug for this?
Usually this is true, but ctypes is special. It lets you make pretty
much unrestricted C calls from Python. We can't guard against all of
those.
Tom
next prev parent reply other threads:[~2011-04-13 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 9:44 Christoph Mathys
2011-04-12 21:17 ` Phil Muldoon
2011-04-13 7:22 ` Christoph Mathys
2011-04-13 14:27 ` Tom Tromey [this message]
2011-04-13 14:26 ` 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=m31v162pms.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eraserix@gmail.com \
--cc=gdb@sourceware.org \
--cc=pmuldoon@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