From: Roland Schwingel <roland.schwingel@onevision.de>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sources.redhat.com
Subject: Re: Current Status of Insight
Date: Fri, 13 May 2005 08:14:00 -0000 [thread overview]
Message-ID: <428461A5.4050803@onevision.de> (raw)
Hi...
> > Or should I use DDD (which i dont really like, because i think Motif
> > must have been designed by people that had no eyes, and was then hit
> > with the ugly stick 3 times on birth. [Personal opinion, Motif guys if
> > you like how it looks, more power to you])
>
> DDD, Eclipse CDT, xgdb (and friends) are all still options. I admit,
> though, I still use Insight from CVS head. IMO, it will be quite some
> time before something can match the simplecity of the UI and the speed
> of insight.
I also use Insight from CVS head. It works well, and at present
it is for me the *one and only* solution to debug gcc compiled code
on windows! I also tried DDD on cygwin but it is not that reliable.
> The real question is: Is it worth it? Does anyone really care anymore?
YES YES YES!!!! I am building insight from CVS frequently to run
on windows. Beside of the stack dump problem in gdb 6.x itself it works
really great!!! I use Insight on cygwin to debug mingw code all day!
> At one time I considered branching, dumping all the Tcl code (assigned
> to Red Hat) and rewriting in some form of gtk (all new code assigned to
> FSF). I don't believe there is enough interest to justify this work,
> though.
Well a replacement GUI would be nice, but should IMHO run also on
windows/cygwin.
Roland
next reply other threads:[~2005-05-13 8:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 8:14 Roland Schwingel [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-17 8:26 Roland Schwingel
2005-05-17 10:18 ` Steven Johnson
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
[not found] <1115992411.3092.ezmlm@sources.redhat.com>
2005-05-13 15:44 ` E. Weddington
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-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=428461A5.4050803@onevision.de \
--to=roland.schwingel@onevision.de \
--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).