From: Keith Seitz <keiths@redhat.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: insight@sourceware.org
Subject: Re: Insight development?
Date: Mon, 03 May 2010 16:41:00 -0000 [thread overview]
Message-ID: <4BDEFC92.5050505@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1005031434140.15683@lnxricardw.se.axis.com>
On 05/03/2010 05:35 AM, Ricard Wanderlof wrote:
> It seems that not much has happened with Insight lately - the latest
> news on the Insight home page (http://sourceware.org/insight/) is about
> 6.8-1 from July last year. Has development of Insight stopped
> completely, or are people just busy with other things?
Active development has pretty much stopped entirely. As far as I know, I
am the only person still actively trying to keep insight crawling along
-- largely because I still use it daily for my work.
Occasionally a gdb person will check in a patch for some API change that
is made upstream, but those people are very few.
Releases get done very sporadically. I've been sitting on a configury
patch for x86_64 for some time. Since I am now migrating to an x86_64
box, I can actually now test this stuff! [And there have been numerous
problems reported with x86_64.]
And in general, I have been very busy with my personal interests, so
it's a real effort to do much more than keep it working sufficiently for
my needs.
I've thought about rewriting from scratch, but there are several
competing projects out there like nemevier that require consideration
first. Perhaps I will just jump ship and work one of those.
Keith
next prev parent reply other threads:[~2010-05-03 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 12:35 Ricard Wanderlof
2010-05-03 16:41 ` Keith Seitz [this message]
2010-05-03 18:58 ` Christopher Faylor
2010-05-06 19:55 ` Johan
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=4BDEFC92.5050505@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=ricard.wanderlof@axis.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).