X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <5195c8761001180252i6afffb3m4aa0a9d9fea85580@mail.gmail.com> References: <5195c8761001180247sb63f867sfaf1696c3b9a21ca AT mail DOT gmail DOT com> <5195c8761001180252i6afffb3m4aa0a9d9fea85580 AT mail DOT gmail DOT com> Date: Mon, 18 Jan 2010 13:45:24 +0100 Message-ID: <6910a61001180445r4f10b8cay43e19d887fdac3bd@mail.gmail.com> Subject: Re: Gitk issue post 1.7.1 upgrade From: Reini Urban To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 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 2010/1/18 Jeenu V: > I'm using Gitk from Cygwin and I come across this problem quite > frequently post upgrade to 1.7.1. While I'm viewing commits a pop-up > appears saying "writing to stdout fails". I'm able to consistently > reproduce it by making quick random clicks on the commit graph. And I > don't remember seeing this behavior pre-1.7.1 Cygwin. > > I've captured log and is attached. Has any one else come across this? me too. :) Another gitk issue I have: Saved patches/commits are stored with permissions 0000. This seems to be a win32 tk/tcl issue. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple