From: Tom Tromey <tromey@redhat.com>
To: Project Archer <archer@sourceware.org>
Subject: remaining python bits
Date: Wed, 30 Jun 2010 17:22:00 -0000 [thread overview]
Message-ID: <m3iq50sae5.fsf@fleche.redhat.com> (raw)
Phil wanted a list of stuff from archer-tromey-python that hadn't yet
been ported.
I don't remember everything, I think a merge + diff would be more
complete. Stuff I do remember:
* linespec decoder function. This is handy if you want to write certain
kinds of commands in python.
* The "-P" argument that lets you start write gdb script in Python.
* The code to let users post a Python function into the gdb event queue.
This is necessary if you want to write a multi-threaded Python app on
top of gdb. E.g., handy if you want to do GUI stuff.
* The script library. I think most of these are useful, but some
require some redesign first (e.g., new-backtrace -- there was a thread
about this).
Tom
reply other threads:[~2010-06-30 17:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3iq50sae5.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).