[Top][All Lists]

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

[Octave-bug-tracker] [bug #44360] segfault in test ov-class.cc-tst

From: Rik
Subject: [Octave-bug-tracker] [bug #44360] segfault in test ov-class.cc-tst
Date: Sun, 01 Mar 2015 04:52:27 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0

Update of bug #44360 (project octave):

                  Status:          Ready For Test => Works For Me           
                 Summary: segfault in test __osmesa_print__.cc-tst => segfault
in test ov-class.cc-tst


Follow-up Comment #16:

Re-titling report.  None of the gdb backtraces show a problem with
__osmesa_print__.cc.  Rather it is tests in ov-class.cc that are the issue.

In terms of testing, since the original reporter is running from Mercurial
sources it will be faster to run the individual failing tests, rather than
running 'make check'.  The following should do this

./run-octave -g -f --no-gui-libs
(gdb) run
octave:1> test ov-class.cc

I assume this will fail.  But if it doesn't, then we probably need to look at
the other test failures with the audio tests.

One thing I notice is that the backtrace suggests a Java SE 8 virtual machine.
 Almost all of the testing to date has been with Java SE 7.  Who knows whether
this important, but the Wikipedia entry for SE 8 says that there are now
statically linked JNI libraries.  That might affect Octave.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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