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:message-id:date:from:subject:to:references
	:content-type; q=dns; s=default; b=KVs4nlGIVCSziEAb5j7TDgcUyscID
	zp/EJqoNbiiZOzM9ApoIwo9JqFaQEs4oj4AkVCUpmZaFNhK99UHrLvip45IbsWOv
	xMpI1LVLbUY/fKOOSER72+TZN5nl836YvOqM6JP3apjP7+DFMhpIipWLXEuEVbqw
	51n84Hft6pD/GA=
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:message-id:date:from:subject:to:references
	:content-type; s=default; bh=SFp0sxjf+ho43W6SvL2KEwKJtYA=; b=do7
	ztj/o4JsJLdnuXpbHuJa/fiXBgi10e/jBYCRQRGAQli4stcY+Ebge3NFH7K+Ac9s
	8UIM+V8NHp82PK54JoUwlpdg7XOLyr4CY7YY0uri8aZBsjJvrZs7scAF1ci4py/k
	Pn4SrBOh8QoP1lStfNZCK+ioF8T6AO4POFAzxIxI=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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.3 required=5.0 tests=BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=2.28.1, Martchus, UD:msg00229.html, msg00289html
X-HELO:	mail-oi0-f46.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:subject:to:references :user-agent; bh=HbaiStbJ+RI/TvxlzGGABLO0Nph/pC2Pn75fmgrF02M=; b=b8J2QvukRQ+8BABH6THaLO21NAFEcIdUhefwq/mH/7C2aq1HF0Lg1rk+nOMU+EckP6 MKSXxLBaclwsBzHpZerbmwefw2qpJqQtg05BZjZG4rBMsOdSCVE694+IXFx4F+kHa4D5 D4WEHhHzuea3yZb+0IrTYIyVgpDldB93ZuEBW5KEYM8cc3Bki1F5wTiqHqdJmTiSpSPW vDpywHvENzuOlCDnMDIBBjdiD/wKdU4HIs2PLi9sf5KcX/bvX32X3zKgsMNS37bWxbRa JvwPn5ESN8hF1T4dJOU/wT9XWolsdFr6roZK0iYHWb1lRxMB05I7nW3mSozGWGH/Zyhk eh/w==
X-Gm-Message-State:	AMCzsaWTx9wwC6EiVv5LhUMq6OXG3oN+ybPa1ssh3WRJqgZqUeIHJJnZ xjU9Ten1TjMD/GPw+iASnTg1sg==
X-Google-Smtp-Source:	AOwi7QDdq/BzS/x5vhYBfkO5C95Ne5OFq/gNi7QyC1lpmDCTd+Z5t53MBy5ntTzZ19j+3c7YuDHdeg==
X-Received:	by 10.157.72.169 with SMTP id d38mr10914693otf.324.1507080511428; Tue, 03 Oct 2017 18:28:31 -0700 (PDT)
Message-ID:	<59d4393e.566cca0a.9340.af3b@mx.google.com>
Date:	Tue, 03 Oct 2017 18:28:30 -0700 (PDT)
From:	Steven Penny <svnpenn AT gmail DOT com>
X-Google-Original-From:	Steven Penny
Subject:	Re: Segmentation fault with binutils 2.28.1
To:	cygwin AT cygwin DOT com
References:	<81506abd-3ad6-94e7-9915-906756b3651e AT gmail DOT com>
User-Agent:	Tryst/2.0.1 (github.com/svnpenn/tryst)

On Tue, 3 Oct 2017 14:37:04, Marco Atzeri wrote:
> you wrote nothing at all. So it is difficult to understand what is your exact
> issue

I wrote it 4 times:

- http://cygwin.com/ml/cygwin/2017-09/msg00229.html
- http://cygwin.com/ml/cygwin/2017-09/msg00289.html
- http://cygwin.com/ml/cygwin/2017-10/msg00021.html
- http://github.com/Martchus/tageditor/issues/23#issuecomment-331757730

Here though, let me write it 5 now:

    $ cat z.cpp
    #include <iostream>
    main() {
      std::cout << "cout test\n";
    }

    $ x86_64-w64-mingw32-g++ -static -o z z.cpp

    $ ./z
    Segmentation fault

> as in the past you blamed the compiler.

Yes, I discovered new information, so I modified the email subject to reflect
that. Would you rather me continue to blame the complier, or try to help
diagnose the problem?

> Error report should be clear and complete;

Example above is MCVE http://stackoverflow.com/help/mcve

> only links to other place are not enough.

See above - also notice carefully that example was included in my previous post
as well

> I saw the comment from Martchus
> "Note that when I had been using mingw-w64-binutils 2.28 (before recent 
> update to 2.29) I didn't encounter this issue. I never tried 2.28.1."
> 
> So it does not seem an issue specif of 2.28

No one but you has said that 2.28 has a problem. What Martchus actually said
was:

- 2.28   working
- 2.28.1 never tried
- 2.29   working

> Have you built it ?

No

> Or are you only asking Jon to dedicate his time ?

Hm. Last I checked I have already made at least 10 posts on this issue:

- http://cygwin.com/ml/cygwin/2017-09/msg00195.html
- http://cygwin.com/ml/cygwin/2017-09/msg00218.html
- http://cygwin.com/ml/cygwin/2017-09/msg00229.html
- http://cygwin.com/ml/cygwin/2017-09/msg00247.html
- http://cygwin.com/ml/cygwin/2017-09/msg00248.html
- http://cygwin.com/ml/cygwin/2017-09/msg00282.html
- http://cygwin.com/ml/cygwin/2017-09/msg00289.html
- http://cygwin.com/ml/cygwin/2017-09/msg00294.html
- http://cygwin.com/ml/cygwin/2017-10/msg00021.html
- http://cygwin.com/ml/cygwin/2017-10/msg00025.html

Maybe your sense of time is distorted.

> Last time I had issue with cygwin binutils 2.25, I built the 2.28.90
> and I verified that was solving the issue I saw.
> I was not just expecting Jon to debug it alone.

Good for you, but I dont have to build anything to verify the issue - I narrowed
the problem to a single package, and tested with "Test" and "Current" versions.
"Current" works - "Test" fails.

So we could patch "Test", but since a newer version is already available (2.29),
the sane thing to do would be to just upload a newer test version and probably
bypass the problem altogether. If you want to waste your time making a build in
this case that is your business, but dont put that bad advice off on me when I
have already diagnosed the problem.


--
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

- Raw text -