From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 52952 invoked by alias); 12 May 2015 10:36:02 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 52941 invoked by uid 89); 12 May 2015 10:36:01 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_40,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-qg0-f50.google.com Received: from mail-qg0-f50.google.com (HELO mail-qg0-f50.google.com) (209.85.192.50) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Tue, 12 May 2015 10:36:00 +0000 Received: by qgfi89 with SMTP id i89so1216987qgf.1 for ; Tue, 12 May 2015 03:35:58 -0700 (PDT) X-Received: by 10.140.235.68 with SMTP id g65mr19840233qhc.96.1431426958695; Tue, 12 May 2015 03:35:58 -0700 (PDT) Received: from [172.21.188.214] ([149.6.156.42]) by mx.google.com with ESMTPSA id f64sm12861300qhc.37.2015.05.12.03.35.57 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 May 2015 03:35:58 -0700 (PDT) Message-ID: <5551D784.407@gmail.com> Date: Tue, 12 May 2015 10:55:00 -0000 From: Marco Atzeri User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Stderr Ouput borken im mintty 1.1.3 in cygwin 2.0.0 under Windows 7 64 bit References: <5551D251.4050203@geophysik.uni-kiel.de> In-Reply-To: <5551D251.4050203@geophysik.uni-kiel.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-05/txt/msg00136.txt.bz2 On 5/12/2015 12:13 PM, Nils Holzrichter wrote: > Dear all, > > I have a problem using mintty. It does not output text send to stderr > when it's short and truncates long stderr output. This is true for > Windows binaries, but not for cygwin binaries. > The stderr output to shell works if bash is started directly, but if a > stderr message of 360 lines is written to file, only 315 lines appear. > > Can somebody help me? > > best regards > > Nils Holzrichter > do you have a test case ? Regards Marco -- 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