From: Tom Tromey <tromey@redhat.com>
To: Jason Ekstrand <jason@jlekstrand.net>
Cc: gdb@sourceware.org
Subject: Re: GDB Python API issues
Date: Mon, 07 Nov 2011 13:28:00 -0000 [thread overview]
Message-ID: <m3wrbcnjtb.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAOFGe94qCnG=FUn07VhegVQJOm4swPKfnA7=NFvSuZy39VUM6Q@mail.gmail.com> (Jason Ekstrand's message of "Sat, 5 Nov 2011 21:55:17 -0500")
>>>>> "Jason" == Jason Ekstrand <jason@jlekstrand.net> writes:
Jason> Hi, I've used GDB for a quite a while now, but have never dug into GDB
Jason> development. Recently, I started working on a project that heavily
Jason> abuses GDB's python API. I'm trying to essentially write a more
Jason> up-to-date replacement for DDD that, instead of parsing GDB output or
Jason> tying directly into it on a C level, pulls data from inside using
Jason> GDB's python API.
You could also simply put the GUI inside of gdb... :)
The 'gdb.post_event' function basically exists so you can do this and
run the GUI in a separate thread.
Jason> As I've been working on this project, I've started to find all sorts
Jason> of use cases that the API, as it currently stands, doesn't seem to
Jason> support. I'm willing to help, but I don't quite know where to start
Jason> and I wanted to talk to someone before I start submitting a stream of
Jason> bug reports.
You can bring up ideas and problems here on the list if you like.
A stream of bug reports would also be ok.
Tom
next prev parent reply other threads:[~2011-11-07 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 2:55 Jason Ekstrand
2011-11-06 4:51 ` Hui Zhu
2011-11-07 13:28 ` Tom Tromey [this message]
2011-11-07 13:35 ` Phil Muldoon
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=m3wrbcnjtb.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=jason@jlekstrand.net \
/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