From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 86288 invoked by alias); 27 Nov 2016 03:04:32 -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 86154 invoked by uid 89); 27 Nov 2016 03:04:20 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_50,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 spammy=H*r:8.12.10, H*Ad:D*cornell.edu, February, Girish X-HELO: limerock01.mail.cornell.edu Received: from limerock01.mail.cornell.edu (HELO limerock01.mail.cornell.edu) (128.84.13.241) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 27 Nov 2016 03:04:10 +0000 X-CornellRouted: This message has been Routed already. Received: from authusersmtp.mail.cornell.edu (granite4.serverfarm.cornell.edu [10.16.197.9]) by limerock01.mail.cornell.edu (8.14.4/8.14.4_cu) with ESMTP id uAR347iv032595 for ; Sat, 26 Nov 2016 22:04:08 -0500 Received: from [192.168.1.5] (mta-68-175-148-36.twcny.rr.com [68.175.148.36] (may be forged)) (authenticated bits=0) by authusersmtp.mail.cornell.edu (8.14.4/8.12.10) with ESMTP id uAR345BC013413 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Sat, 26 Nov 2016 22:04:06 -0500 Subject: Re: Application not working in 64-bit cygwin cygwin/X To: cygwin@cygwin.com References: From: Ken Brown Message-ID: <39a3c4f5-7d98-f24a-a21b-1cbe4ce1ec8f@cornell.edu> Date: Mon, 28 Nov 2016 07:07:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Cornell-Gauge: Gauge=XXXXX X-PMX-CORNELL-AUTH-RESULTS: dkim-out=none; X-IsSubscribed: yes X-SW-Source: 2016-11/txt/msg00304.txt.bz2 On 11/26/2016 6:51 PM, Girish Joglekar wrote: > I had submitted a possible bug report in March 2016 and a link to tar > file with source code. David Stacey had reproduced my problem. I > downloaded the latest version of cygwin two days ago. The problem > still persists. Can some one advise me whether I should expect some > help from the cygwin experts. I can submit the source code again if > necessary. If you think your crash is due to a Cygwin bug, then you need to try to write a small test case that exhibits the problem. Marco told you that last February, and this was your reply (https://cygwin.com/ml/cygwin/2016-02/msg00368.html): > The code is so interlinked that it would have taken me > a lot longer to separate out only the relevant code. You have to show some willingness to spend time on this problem yourself if you hope to get help from the Cygwin experts. Ken -- 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