From: Phil Muldoon <pmuldoon@redhat.com>
To: archer@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>
Subject: Re: Some Python bugs
Date: Mon, 19 Oct 2009 10:33:00 -0000 [thread overview]
Message-ID: <4ADC407D.2010206@redhat.com> (raw)
In-Reply-To: <20091013191623.GA19876@caradoc.them.org>
On 10/13/2009 08:16 PM, Daniel Jacobowitz wrote:
> I recently wrote a Python script to search through debug info and
> generate some XML data I needed. Here's a few issues I noticed
> (from memory, please excuse typos):
>
Daniel and I chatted on irc about these bugs/enhancements, and I
volunteered to turn them into bugs so we could track them in bugzilla.
Cheers, Phil
List:
--
GDB.Values do not expose array bounds.
http://sourceware.org/bugzilla/show_bug.cgi?id=10804
GDB Type.fields() crashes on non-struct/class types
http://sourceware.org/bugzilla/show_bug.cgi?id=10805
Use ensure_python_env over PyGilState_Ensure
http://sourceware.org/bugzilla/show_bug.cgi?id=10806
Expose macro definitions to GDB Python API
http://sourceware.org/bugzilla/show_bug.cgi?id=10807
Allow GDB/Python API to capture and store GDB output
http://sourceware.org/bugzilla/show_bug.cgi?id=10808
prev parent reply other threads:[~2009-10-19 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 19:16 Daniel Jacobowitz
2009-10-19 10:33 ` Phil Muldoon [this message]
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=4ADC407D.2010206@redhat.com \
--to=pmuldoon@redhat.com \
--cc=archer@sourceware.org \
--cc=drow@false.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).