public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Martin Rakhmanov <rakhmanov.martin@gmail.com>
Cc: insight@sources.redhat.com
Subject: Re: insight-weekly-6.8.50-20081103 fails to compile
Date: Mon, 10 Nov 2008 21:18:00 -0000	[thread overview]
Message-ID: <4918A4DB.2020609@redhat.com> (raw)
In-Reply-To: <4916DBDF.3000709@gmail.com>

Martin Rakhmanov wrote:
> I see no val_print defined which accepts 10 args. How this ever could be 
> checked in?

Because that change was made to gdb, and I was off last week, so I did 
not get a chance to update insight sources yet. I have a patch for this, 
but it is not yet tested, and I need to get back to paying work.

> It looks like the project is almost dead. What is the future for insight?

IMO, there is very little future, but while I'm stuck using gdb for 
debugging, I will always keep insight limping along with the 
functionality I require (which is mostly just the source window, 
locals/watch, console, and bp window). Gdb is changing MUCH faster than 
I can keep up by myself.

As a result, I will probably put insight out to official pasture at the 
end of the year: meaning that I will officially step down as head 
maintainer, leaving that post vacant. The future of snapshots, releases, 
bug database, etc is undetermined. I will probably close/stop almost 
everything. This list will probably be one of the few things that remains.

Heck, with the work that's being done to integrate python into gdb, I 
might just start a new version of insight ((c) FSF this time) using python.

Believe it or not, I still believe we got a lot of things right.

Keith

  reply	other threads:[~2008-11-10 21:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-09 12:48 Martin Rakhmanov
2008-11-10 21:18 ` Keith Seitz [this message]
2008-12-13  1:12 ` Kevin Buettner
2008-12-13 18:13   ` Keith Seitz
2008-12-15 18:07     ` Kevin Buettner

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=4918A4DB.2020609@redhat.com \
    --to=keiths@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=rakhmanov.martin@gmail.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).