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