X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 06 Aug 2008 13:41:35 -0400 To: cygwin AT cygwin DOT com Subject: Re: Does anyone use insight on cygwin? X-Mailer: Virtual Access Open Source http://www.virtual-access.org/ Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: <20080804233810.GA13054@ednor.casa.cgf.cx> References: <20080804233810 DOT GA13054 AT ednor DOT casa DOT cgf DOT cx> Reply-To: cygwin AT cygwin DOT com From: Brian Keener X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Let me change my previous response please - I use both Insight and gdb. I prefer Insight and I don't have a problem with Insight running in X although I would hate to loose the version that runs from the bash prompt and force me to always run in X. An X version and regular version would be great - if possible. Especially now that I found my issue - my debug version of Cygwin1.dll (self compiled) apparently broke Insight and/or Tcl/Tk because as soon as I changed back to a released Cygwin1.dll - Insight started working again from bash. Just wanted to clarify. Thanks for everything folks. bk -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/