X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Thu, 07 Aug 2008 14:28:55 -0400 To: cygwin@cygwin.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: <489A47A8.3000902@byu.net> References: <20080804233810.GA13054@ednor.casa.cgf.cx> <001a01c8f7ee$de8feaf0$9601a8c0@CAM.ARTIMI.COM> <489A47A8.3000902@byu.net> Reply-To: cygwin@cygwin.com From: Brian Keener X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Eric Blake wrote: > ccording to Brian Keener on 8/6/2008 2:44 PM: > | my debug version of Cygwin1.dll running Insight would get a Tcl/TK error > | looking for the init file. Changing back to the released non debug version > | fixed it. > > And just when was your cygwin1.dll built? This has been fixed in CVS, but > only within the last week or so (ie. there was a window where the 1.7.0 > dll would spawn tcl in such a way that it failed to initialize properly, > because it was unprepared for wide-char information). You are correct - my dll was built prior to that and cvs update and fresh build last evening revealed that in fact Insight was again working with my debug dll. I was going to post that very fact this am but you beat me to it. :-) 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/