public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "E. Weddington" <ericw@evcohs.com>
To: sjohnson@sakuraindustries.com
Cc: insight@sources.redhat.com
Subject: Re: Current Status of Insight
Date: Fri, 13 May 2005 15:44:00 -0000	[thread overview]
Message-ID: <4284CB51.1050605@evcohs.com> (raw)
In-Reply-To: <1115992411.3092.ezmlm@sources.redhat.com>

[Apologies for breaking any threading. Thunderbird cannot yet respond to 
individual mails in a digest! Please CC me in any reply.]

> It seems that there is at least 6 people that care:
>
> (in no particular order, and sorry if i list you and you dont really 
> care)
>
> 1. Keith Seitz
> 2. Duane Ellis
> 3. Roland Schwingel
> 4. Paul Schlie
> 5. Christopher Faylor
> 6. Steven Johnson (me)
> And Maybe (although it is less than clear from their posts):
> 7. Nickolay Kolchin
> 8. Jon Beniston
>
> Anybody else care to add their name to this list of people that care 
> about, or at the very least use a version of insight and would like to 
> see it continue in some form. 

Add my name.

I build Insight/GDB and include it in the WinAVR package:
<http://sourceforge.net/projects/winavr>
Which is a suite of open source cross development tools targetting the 
AVR and hosted on Windows. Note that one of the previous releases of 
WinAVR has had over 42,000 downloads.

WinAVR is designed for Windows users, and there are a lot of them where 
WinAVR is their first exposure to the GNU toolchain. A lot of Windows 
users prefer to have GUI based tools. Insight is absolutely critical in 
this area as it may be a users first exposure to using GDB. If they get 
comfortable with using the Insight interface, then that can lead them to 
using the power of the CLI interface of raw GDB.

Unfortunately, most of my interest in Insight is as a 
builder/redistributor, not so much as a developer. But it would be 
incredibly unfortunate if Insight were to go away. As it is, I've been 
stuck on building Insight 6.1 (with minimal patches), since there's been 
no further release tarballs. I have yet to jump into building from CVS HEAD.

My concern with forking the project is, IIUC, the fact that GDB and 
Insight closely coupled. Keith, anybody, correct me if I'm wrong, but 
the Insight executable contains all of GDB. It's not like Insight is a 
separate GUI program that calls a separate GDB program. Unfortunately, 
one of down sides to having this close coupling is the fact that Insight 
has not in the past been able to be built as a native Win32 executable 
without Cygwin. Yes, I saw the recent thread on the gdb list about 
building gdb for Windows without Cygwin; I'd rather not go over that 
again. I just want to throw out that there could be advantages about 
having the GUI decoupled from GDB, especially if forked.

Eric Weddington


       reply	other threads:[~2005-05-13 15:44 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1115992411.3092.ezmlm@sources.redhat.com>
2005-05-13 15:44 ` E. Weddington [this message]
2005-05-13 17:15   ` Christopher Faylor
2005-05-13 17:35     ` Bernhard Walle
2005-05-13 17:45       ` Christopher Faylor
2005-05-13 17:58         ` Bernhard Walle
2005-05-13 21:51           ` Fernando Nasser
2005-05-14 14:54             ` Duane Ellis
2005-05-14 17:25               ` Bernhard Walle
2005-05-17 19:38               ` Fernando Nasser
2005-05-17  8:26 Roland Schwingel
2005-05-17 10:18 ` Steven Johnson
  -- strict thread matches above, loose matches on Subject: below --
2005-05-16 23:45 Paul Schlie
2005-05-14 22:13 Paul Schlie
2005-05-16  5:35 ` Steven Johnson
2005-05-17 19:33   ` Fernando Nasser
2005-05-16 16:10 ` Christopher Faylor
2005-05-16 17:18   ` Paul Schlie
2005-05-13  8:14 Roland Schwingel
2005-05-13  1:15 Paul Schlie
2005-05-12 10:07 Steven Johnson
2005-05-12 10:13 ` Jon Beniston
     [not found]   ` <2636500f05051203276a294e8f@mail.gmail.com>
2005-05-12 10:29     ` Nickolay Kolchin
2005-05-12 15:17 ` Keith Seitz
2005-05-12 21:46   ` Steven Johnson
2005-05-12 22:42     ` Duane Ellis
2005-05-12 22:45     ` Duane Ellis
2005-05-13  2:09     ` Christopher Faylor
2005-05-13  2:19       ` Keith Seitz
2005-05-13 13:53         ` Steven Johnson
2005-05-13 14:05           ` Christopher Faylor
2005-05-13 14:18             ` Jon Beniston
2005-05-13 14:21               ` Christopher Faylor
2005-05-13 14:16           ` Hans W. Horn
2005-05-13 14:29             ` Christopher Faylor
2005-05-13 14:33           ` James Lemke
2005-05-14 11:14           ` Nickolay Kolchin
2005-05-17 12:51             ` Fernando Nasser
2005-05-16 22:07         ` Steven Johnson

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=4284CB51.1050605@evcohs.com \
    --to=ericw@evcohs.com \
    --cc=insight@sources.redhat.com \
    --cc=sjohnson@sakuraindustries.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).