[Octave-bug-tracker] [bug #51436] Segmentation fault when running make check-local on 32-bit (with gcc7)

[John W. Eaton]

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

Can you find where it crashes?  It seems this would be independent of the GUI,
so the easiest way to get a stack trace might be to use "./run-octave -g" and
then run the test individually from the prompt.  Something like


./run-octave -g
...
(gdb) run
...
octave> x = javaObject ("java.lang.Object");
octave> test libinterp/corefcn/lu.cc-tst
... and, assuming the segfault happens:
(gdb) where


It still could be a problem with the way we initialize the JVM or whether we
are properly saving/restoring CPU modes.  As I recall, some JVM
implementations like to set floating point rounding modes and such.  Maybe
there is something else we are missing there?


    _______________________________________________________

Reply to this item at:

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

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