From: Tom Tromey <tromey@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Insight List <insight@sources.redhat.com>
Subject: Re: insight build, plus patch request
Date: Mon, 14 Jul 2008 20:54:00 -0000 [thread overview]
Message-ID: <m3vdz85grp.fsf@fleche.redhat.com> (raw)
In-Reply-To: <487BBA39.1050207@redhat.com> (Keith Seitz's message of "Mon\, 14 Jul 2008 13\:42\:33 -0700")
Keith> Good case for PyGtk, for sure, but unless I went with 100% GDB/MI
Keith> implementation (which I don't want to do), I would still need to
Keith> either rewrite or recycle all the glue code in gdbtk/generic.
I think we'll need that stuff anyhow, just for plain Python
scripting in gdb. Some of the hooks are in weird spots, but a lot of
them just seem like natural places to want to get information or
insert some processing.
Keith> Once again, it may simply not be worth the effort any more. It might
Keith> be better to simply contribute to Øyvind Harboe's stand-alone CDT
Keith> debugger.
Or nemiver or kdevelop or ... :-)
Tom
next prev parent reply other threads:[~2008-07-14 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 19:35 Tom Tromey
2008-07-14 19:47 ` Keith Seitz
2008-07-14 20:30 ` Tom Tromey
2008-07-14 20:43 ` Keith Seitz
2008-07-14 20:54 ` Tom Tromey [this message]
2008-07-15 9:56 ` Andrew STUBBS
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=m3vdz85grp.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=insight@sources.redhat.com \
--cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).