public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: "'Jingzhao Ou'" <jingzhao.ou@gmail.com>,
	"'Keith Seitz'" <keiths@redhat.com>
Cc: <insight@sources.redhat.com>
Subject: RE: Compiling the latest GDB on cygwin
Date: Fri, 19 Aug 2005 09:22:00 -0000	[thread overview]
Message-ID: <SERRANOmyCF1Hkikieq00000152@SERRANO.CAM.ARTIMI.COM> (raw)
In-Reply-To: <4304CDA9.4040100@gmail.com>

----Original Message----
>From: Jingzhao Ou
>Sent: 18 August 2005 19:04

> Keith Seitz wrote:
>> I
>> believe insight has outlived its usefulness, and most people are moving
>> onto other gdb front-ends. 

> Regarding the usefulness of Insight, there is some good news. The
> Embedded Development Kit (EDK) from Xilinx (the largest company in
> reconfigurable hardware, http://www.xilinx.com/) uses Insight. I believe
> quite some researchers and engineers in the reconfigurable computing
> area are using Insight for embedded system development.
> 
> Also, if you know about ModelSim from Mentor Graphics
> (http://www.model.com/), you will see that Tcl/Tk is very important in
> the EDA (Electronic Design Automation) world. Based on Tcl/Tk, I believe
> that Insight makes a lot of sense in EDA. For example, it is very
> suitable for tool integration issues.

  Let me second that!  I quite *like* the insight gui, and we also use
modelsim tcl/tk at my workplace!

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

      reply	other threads:[~2005-08-19  9:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16  6:39 Jingzhao Ou
2005-08-16 12:03 ` Dave Korn
2005-08-16 20:48   ` Jingzhao Ou
2005-08-17 15:48     ` Dave Korn
2005-08-17 22:21       ` Jingzhao Ou
2005-08-17 23:34         ` Jingzhao Ou
2005-08-17 23:43           ` Keith Seitz
2005-08-18  5:35             ` Jingzhao Ou
2005-08-18 17:41               ` Keith Seitz
2005-08-18 18:04                 ` Jingzhao Ou
2005-08-19  9:22                   ` Dave Korn [this message]

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=SERRANOmyCF1Hkikieq00000152@SERRANO.CAM.ARTIMI.COM \
    --to=dave.korn@artimi.com \
    --cc=insight@sources.redhat.com \
    --cc=jingzhao.ou@gmail.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).