octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #51436] Segmentation fault when running make c


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #51436] Segmentation fault when running make check-local on 32-bit (with gcc7)
Date: Mon, 10 Jul 2017 23:41:44 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0

Follow-up Comment #3, bug #51436 (project octave):

Agree with Dmitri, please try building and running tests without OpenBLAS to
see if that makes a difference.

Both Debian-based and Fedora-based distributions are building Octave 4.2.1 and
running the test suite without problems. Both build with netlib BLAS and
LAPACK, not OpenBLAS.

https://buildd.debian.org/status/fetch.php?pkg=octave&arch=i386&ver=4.2.1-2&stamp=1498828904&raw=0

https://kojipkgs.fedoraproject.org//packages/octave/4.2.1/3.fc27/data/logs/i686/build.log

FWIW I can reproduce this crash or a similar crash during the test suite by
building against OpenBLAS on a 32-bit i686 VM. It seems to occur most often in
the DGETRF function, which pushes the blame towards OpenBLAS. It also only
seems to occur after the Java runtime is loaded. Both OpenBLAS and the JVM
start a number of background threads when they are initialized.

For example this does not crash


$ ./run-octave -WqfH --eval 'test libinterp/corefcn/lu.cc-tst'


but this does


$ ./run-octave -WqfH --eval 'x = javaObject ("java.lang.Object"); test
libinterp/corefcn/lu.cc-tst'


And both of these crash regardless of the value of OMP_NUM_THREADS.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51436>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]