public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Insight List <insight@sources.redhat.com>
Subject: Re: insight build, plus patch request
Date: Mon, 14 Jul 2008 20:43:00 -0000	[thread overview]
Message-ID: <487BBA39.1050207@redhat.com> (raw)
In-Reply-To: <m37ibo6wf0.fsf@fleche.redhat.com>

Tom Tromey wrote:
>>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:
> 
> Keith> Methinks Insight's usefulness is coming to an end.
> 
> Time for that PyGtk rewrite... :)

I already started playing with that. Alas, with the "new" frysk ("new" 
GDB?) coming up, I am not so sure that it is worth it.

Let's face it: Insight is in need of massive rewriting, barely 
maintained, not developed, and is in licensing limbo. This last con is 
enough to kill Insight IMO. Heck, it probably *has* been one of the 
reasons why Insight is so stagnant (at least it is for me).

Good case for PyGtk, for sure, but unless I went with 100% GDB/MI 
implementation (which I don't want to do), I would still need to either 
rewrite or recycle all the glue code in gdbtk/generic.

Once again, it may simply not be worth the effort any more. It might be 
better to simply contribute to Øyvind Harboe's stand-alone CDT debugger.

Keith

  reply	other threads:[~2008-07-14 20:43 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 [this message]
2008-07-14 20:54       ` Tom Tromey
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=487BBA39.1050207@redhat.com \
    --to=keiths@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=tromey@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).