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:from:to:references:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=LZILraXOJZVPTSmh
	dyNqDInwyBtlJbD+SpvSeXgD4bZgrw656reOoqr8Yaa90Sf6Xd8hUfyXH60yk+rX
	uufLSOnghryNHAGLyFzDam41lBc6qQe7txR0zGVPtF2VHW7xsZD3SxG4R+8/9TAQ
	BUb4Fyl/EY/EgrIf80P/0SMttqo=
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:from:to:references:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=LfcB16JdAlAYHtM22P1TSL
	tGVlM=; b=RLDOfsVcbJFitnAry6cC7lxNTyYavbdOdFmbKMuvTTy1rzni3lH1l5
	1PB/9ewNIwYIJ8lXYx8PRsjK3JojkmdhEGI4p9ZP/RjtMTNs8WCJqg56O9FLGh6I
	Y5T3RNzQ1aFXktt+ctmQtbJSKkXQIw2HzC6Wh2g0YvrMkBY2T8d2c=
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=-2.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=HX-Languages-Length:1084, intrigued, HContent-Transfer-Encoding:8bit
X-HELO: mailout03.t-online.de
Subject: Re: headache on build repeatibility: octave vs BLODA ?
From: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= <HBBroeker AT t-online DOT de>
To: cygwin AT cygwin DOT com
References: <2904b4fa-6349-bd3e-c4ff-4b32a0bb3838 AT gmail DOT com> <f2d0d267-cca2-bec4-e6a4-1a8d64ebff57 AT t-online DOT de>
Message-ID: <2f4dbec1-1e3d-3930-3a99-08aa1e8353df@t-online.de>
Date: Wed, 29 Jan 2020 01:38:56 +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: <f2d0d267-cca2-bec4-e6a4-1a8d64ebff57@t-online.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes

Am 29.01.2020 um 01:02 schrieb Hans-Bernhard Bröker:

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

This is getting curiouser.

I was intrigued that the stackdump file written was not from 'octave' 
per se, but rather 'octave-cli'.  And indeed some further experiments 
shows that

../../inst/usr/bin/octave-cli-5.1.0.exe --norc --silent --no-history -p 
mex ../../src/octave-5.1.0/test/fntests.m ../../src/octave-5.1.0/test

fails, while

../../inst/usr/bin/octave-5.1.0.exe --norc --silent --no-history -p mex 
../../src/octave-5.1.0/test/fntests.m ../../src/octave-5.1.0/test

passes.  I don't see how 'run-octave' would end up running octave-cli, 
though, unless it had been given the option '-cli'.

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