From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9723 invoked by alias); 29 Jan 2020 00:39:08 -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 9714 invoked by uid 89); 29 Jan 2020 00:39:07 -0000 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 Received: from mailout03.t-online.de (HELO mailout03.t-online.de) (194.25.134.81) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 29 Jan 2020 00:39:06 +0000 Received: from fwd13.aul.t-online.de (fwd13.aul.t-online.de [172.20.27.62]) by mailout03.t-online.de (Postfix) with SMTP id 52DA842112B2 for ; Wed, 29 Jan 2020 01:39:03 +0100 (CET) Received: from [192.168.178.26] (Gh5QTQZDQhYWNmvk+58mRsBpBKQ51z1t7zih4HheqYbG2I3FOQ10Wpg6rffSUshQJT@[79.228.65.18]) by fwd13.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1iwbNg-1K3Amm0; Wed, 29 Jan 2020 01:38:56 +0100 Subject: Re: headache on build repeatibility: octave vs BLODA ? From: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= To: cygwin@cygwin.com References: <2904b4fa-6349-bd3e-c4ff-4b32a0bb3838@gmail.com> Message-ID: <2f4dbec1-1e3d-3930-3a99-08aa1e8353df@t-online.de> Date: Wed, 29 Jan 2020 00:39:00 -0000 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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2020-01/txt/msg00285.txt.bz2 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