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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=hg+varT8byIJ6Ke8
	7oDeZUxGEwClGfEWvLzKazq8IAFt1PjN/ew2hYLfqJhdNfYlf8uUB9wZQKwVXGU2
	CwUs7K7aAqD8Vfl0Ro16KvASAaztsRgCn6/yb34M2ql4rfOMofxdVtRIhhnjDxMg
	Pbj0C1kDyVo/rKe+Pv/+rPRHSgY=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=nWsYdGCCUMGWR5mG7hExFG
	jzp1k=; b=yeDdJ8zxxsYJau4epAMGJX9kYaYt0nwmPFlTkpjZ6RDx1Gwwn4RGHE
	qp304MluJDGUNSTbYaXijJ6Scv+2IGhzJGtVyfOFWbeY5PNplGpO1wh8K0YqI4t6
	Y337HMSGx2qLcbmhC8LPNurZ+mDHcgpo8nGQKagz9n99ddpUm7Sxc=
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-Spam-SWARE-Status:	No, score=-4.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,GIT_PATCH_2,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=ton, HContent-Transfer-Encoding:8bit
X-HELO:	mailout12.t-online.de
Subject:	Re: headache on build repeatibility: octave vs BLODA ?
To:	cygwin AT cygwin DOT com
References:	<2904b4fa-6349-bd3e-c4ff-4b32a0bb3838 AT gmail DOT com>
From:	=?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= <HBBroeker AT t-online DOT de>
Message-ID:	<f2d0d267-cca2-bec4-e6a4-1a8d64ebff57@t-online.de>
Date:	Wed, 29 Jan 2020 01:02:55 +0100
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2
MIME-Version:	1.0
In-Reply-To:	<2904b4fa-6349-bd3e-c4ff-4b32a0bb3838@gmail.com>
X-IsSubscribed:	yes
Note-from-DJ:	This may be spam

Am 25.01.2020 um 17:55 schrieb Marco Atzeri:

>    libinterp/corefcn/file-io.cc-tst 
> ...............................fatal: caught signal Segmentation fault 
> -- stopping myself...
> /bin/sh: line 1:  3771 Segmentation fault      (core dumped) /bin/sh 
> ../run-octave --norc --silent --no-history -p 
> /cygdrive/d/cyg_pub/devel/octave/prova_311_510/octave-5.1.0-2.x86_64/build/test/mex 
> /cygdrive/d/cyg_pub/devel/octave/prova_311_510/octave-5.1.0-2.x86_64/src/octave-5.1.0/test/fntests.m 
> /cygdrive/d/cyg_pub/devel/octave/prova_311_510/octave-5.1.0-2.x86_64/src/octave-5.1.0/test 

> Can anyone try to rebuild the Octave package and let me know
> if the segfault during test is present or not in your system ?

The problem occurs the same way, here, running Win10 Pro 1909 fully 
updated (a.k.a. Version 10.0.18363.592), no extra AntiVirus running 
besides Defender.

> Be aware that build time is very long (~ 4 hours) and requires
> a ton of mathematical libraries.

The build itself completed in ~30 minutes, here ;-).  But then this is a 
fresh i9, 8-core, 16-thread box.

cygport install took ages to complete, though, because objcopy takes 
spectacularly long to strip those DLLs --- longer than it took to build 
the whole package! And it does them one at a time.  That could profit 
from some parallelization.

So while I waited, I decided to try it with the distributed octave.exe 
instead.
It passes the critical tests without issue.

Next step, after cygport inst is done: run the test with the executable 
in cygport's "inst" directory (to bypass libtool): Success, again!

So I tried running the test via libtool, i.e. the run-octave script. 
And boom it goes.

So re-run it in gdb, via libtool (run-octave -g ...).  Still crashes, 
but I didn't manage to get around the SIGSEGV handler in octave.  It 
always caught the SEGV before gdb managed to get there.

So my finding, so far, would be that this is related to libtool.  Maybe 
some update to Windows broke the way libtool interacts with 
not-quite-finished executables...

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