Mon 22 Jun 2015 04:19:00 PM UTC, comment #9:
Wandering why your 2nd backtrace also shows no debugging information for liboctinterp.so.2 I realized that it's the wrong library. Sorry, had I seen this before it probably would have spared you the work ... While your Octave is loaded from a local installation:
Starting program: /usr/local/bin/octave --no-gui-libs
The used liboctinterp is from a system directory:
#8 0x00007fffdef9056b in ?? () from /usr/lib/x86_64-linux-gnu/liboctinterp.so.2
, probably a leftover of a previous Octave installation from a Debian package. This does not only hinder debugging, it may be even the cause of the observed crash (although I wander how it happens that Octave can load the wrong library).
What you can do to test your new Octave without the interfering old library:
If you don't need the Octave from the Deb package, deinstall the Deb package and check that /usr/lib/x86_64-linux-gnu/liboctinterp.so.2 is indeed not present anymore. It may be possible then to use your compiled Octave without recompilation.
If you still need the old Octave, try (without recompilation)
export LD_LIBRARY_PATH="/usr/local/lib"
/usr/local/bin/octave
If this does not help, you could
export LD_RUN_PATH="/usr/local/lib"
(and possibly also: export LD_LIBRARY_PATH="/usr/local/lib")
before
make clean; ./configure; make
of your new Octave.
|