X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:content-type:content-transfer-encoding :mime-version:subject:date:references:to:in-reply-to:message-id; q=dns; s=default; b=qAAC8qlBm6f20ihnrTEBB6wmpxRjEXKPcQvTYPAoP/d aWLdHTMMrLKXU4t0aTOQnYMnv5gzWt6V5+HM4uRXz+7qs+UgsqwUsJG3z4tAJ1nS 0JJAcQibMZEvqsT7FF3nRa7qjQOndPWZ/uOwfb5kGRvX1mZNX1ZdZ+gu1tywQPVU = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:content-type:content-transfer-encoding :mime-version:subject:date:references:to:in-reply-to:message-id; s=default; bh=kQJCoMSux/W66N9TIkFeqquiqlI=; b=tVIP+3Rm9FppWv9wc SwSmAHXKnKyjMUzV2NSLYp1gmcWWQJhponeLG+A4b/+9JJ6m9Ix+n1hBNHXQO9vX DR6FzzGZojY0igYcVrM66rP0bKKmRBLcz97iu/EcoZdQe5B08X/LPxwbZ2/W2AFf 1vzEtutN2O3fwj1iJDyLaQF0qc= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=bet, energy, chase X-HELO: gproxy9.mail.unifiedlayer.com X-Authority-Analysis: v=2.2 cv=QdwWhoTv c=1 sm=1 tr=0 a=x/h8IXy5FZdipniTS+KQtQ==:117 a=x/h8IXy5FZdipniTS+KQtQ==:17 a=IkcTkHD0fZMA:10 a=LWSFodeU3zMA:10 a=w_pzkKWiAAAA:8 a=Yhr3xEn5GATN8rseGhwA:9 a=QEXdDO2ut3YA:10 a=sRI3_1zDfAgwuvI8zelB:22 From: Vince Rice Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Compile/run problems on cygwin not solved by going to cygwin64 Date: Wed, 28 Jun 2017 16:33:39 -0500 References: <86600283-B048-4F1E-AB0D-3512B4044BC3 AT solidrocksystems DOT com> <7802B7F6-8C10-42F1-906E-94BB13EF25A9 AT solidrocksystems DOT com> To: The Cygwin Mailing List In-Reply-To: <7802B7F6-8C10-42F1-906E-94BB13EF25A9@solidrocksystems.com> Message-Id: X-BWhitelist: no X-Exim-ID: 1dQKah-000XL0-KZ X-Source-Sender: rrcs-192-154-176-195.sw.biz.rr.com ([10.1.84.205]) [192.154.176.195]:59741 X-Source-Auth: vrice AT solidrocksystems DOT com X-Email-Count: 4 X-Source-Cap: c29saWRycjI7c29saWRycjI7Ym94ODY3LmJsdWVob3N0LmNvbQ== X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id v5SLXxwc000523 > On 28 June 2017 at 22:02, Vince Rice wrote: >>> On Jun 28, 2017, at 3:00 PM, Wouter van Doorn wrote: >>> … >>> I can't give the strace output, as 'strace ./hello.exe' causes an >>> immediate segmentation fault. No idea why, but not something I'm going >>> to put energy into right now. >> >> You should. If strace won't run, you have a problem, and I would bet the odds of the problems being related (or the same) is pretty high. > > On Jun 28, 2017, at 4:25 PM, Wouter van Doorn wrote: > > Hi Vince, > > If they are related, then solving the problem that's my real current > issue will make the strace one go away. If they are not, then I am > about to start a second wild goose chase. Sticking with the problem > that I am immersed in now in the hope to get that resolved seems to be > my best bet. > > I would like the strace issue to go away, of course, and if someone > has the magic bullet for it I am only too happy to get that issue out > of the way! Please don't https://cygwin.com/acronyms/#TOFU. And https://cygwin.com/acronyms/#PCYMTNQREAIYR. My guess is it would be easier to figure out a segmentation fault than the other. Up to you. -- 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