[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: octave development version from source
From: |
Kjetil brinchmann Halvorsen |
Subject: |
Re: octave development version from source |
Date: |
Thu, 24 Oct 2013 15:01:02 +0200 |
OK! thanks!
I am now trying to follow the instructions on
http://wiki.octave.org/Debugging_Octave
to make a debugging version of octave.
First, I did hg pull /hg update to get todays version, then make
distclean, so configure in a new directory such:
(Part of output)
address@hidden:~/gnuoctave/octave/debug-octave$
../configure FFLAGS=-g CFLAGS=-g CXXFLAGS=-g --enable-bounds-check
--prefix=/opt/dbg-octave
checking Magick++.h usability... yes
checking Magick++.h presence... yes
checking for Magick++.h... yes
checking for Magick::ColorRGB in Magick++.h... yes
checking for GL/gl.h... yes
checking for GL/glu.h... yes
checking for glEnable in -lGL... yes
checking for OpenGL support in FLTK... yes
checking for suitesparse/umfpack.h... yes
checking for umfpack_zi_get_determinant in -lumfpack... no
configure: WARNING: UMFPACK not found. This will result in some lack
of functionality for sparse matrices.
Octave is now configured for x86_64-unknown-linux-gnu
Source directory: .
Installation prefix: /usr/local
C compiler: gcc -Wall -W -Wshadow -Wformat
-Wpointer-arith -Wmissing-prototypes -Wstrict-prototypes
-Wwrite-strings -Wcast-align -Wcast-qual -g -O2 -pthread
C++ compiler: g++ -I/usr/include/freetype2
-Wall -W -Wshadow -Wold-style-cast -Wformat -Wpointer-arith
-Wwrite-strings -Wcast-align -Wcast-qual -g -O2 -pthread
Fortran compiler: gfortran -O
Fortran libraries: -L/usr/lib/gcc/x86_64-linux-gnu/4.8
-L/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu
-L/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib
-L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu
-L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.8/../../..
-lgfortran -lm -lquadmath
Lex libraries:
LIBS: -lutil -lm
AMD CPPFLAGS:
AMD LDFLAGS:
AMD libraries: -lamd
ARPACK CPPFLAGS:
ARPACK LDFLAGS:
ARPACK libraries: -larpack
BLAS libraries: -lcblas -lf77blas -latlas
CAMD CPPFLAGS:
CAMD LDFLAGS:
CAMD libraries: -lcamd
CARBON libraries:
CCOLAMD CPPFLAGS:
CCOLAMD LDFLAGS:
CCOLAMD libraries: -lccolamd
CHOLMOD CPPFLAGS:
CHOLMOD LDFLAGS:
CHOLMOD libraries: -lcholmod
COLAMD CPPFLAGS:
COLAMD LDFLAGS:
COLAMD libraries: -lcolamd
CURL CPPFLAGS:
CURL LDFLAGS:
CURL libraries: -lcurl
CXSPARSE CPPFLAGS:
CXSPARSE LDFLAGS:
CXSPARSE libraries: -lcxsparse
DL libraries: -ldl
FFTW3 CPPFLAGS:
FFTW3 LDFLAGS:
FFTW3 libraries: -lfftw3_threads -lfftw3
FFTW3F CPPFLAGS:
FFTW3F LDFLAGS:
FFTW3F libraries: -lfftw3f_threads -lfftw3f
fontconfig CFLAGS:
fontconfig libraries: -lfontconfig
FreeType2 CFLAGS: -I/usr/include/freetype2
FreeType2 libraries: -lfreetype
GLPK CPPFLAGS:
GLPK LDFLAGS:
GLPK libraries: -lglpk
graphics CFLAGS: -I/usr/include/cairo
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/include/pixman-1 -I/usr/include/freetype2
-I/usr/include/libpng12 -DCP936 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_THREAD_SAFE -D_REENTRANT
graphics libraries: -Wl,-Bsymbolic-functions -lfltk_gl -lfltk -lX11
HDF5 CPPFLAGS:
HDF5 LDFLAGS:
HDF5 libraries: -lhdf5
Java home: /usr/lib/jvm/java-7-openjdk-amd64
Java JVM path:
/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/server
Java CPPFLAGS:
-I/usr/lib/jvm/java-7-openjdk-amd64/include
-I/usr/lib/jvm/java-7-openjdk-amd64/include/linux
Java libraries:
LAPACK libraries: -llapack
LLVM CPPFLAGS:
LLVM LDFLAGS:
LLVM libraries:
Magick++ CPPFLAGS: -I/usr/include/GraphicsMagick
Magick++ LDFLAGS:
Magick++ libraries: -lGraphicsMagick++ -lGraphicsMagick
OPENGL libraries: -lfontconfig -lGL -lGLU
PTHREAD flags: -pthread
PTHREAD libraries:
QHULL CPPFLAGS:
QHULL LDFLAGS:
QHULL libraries: -lqhull
QRUPDATE CPPFLAGS:
QRUPDATE LDFLAGS:
QRUPDATE libraries: -lqrupdate
Qt CPPFLAGS: -I/usr/include/qt4
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui
-I/usr/include/qt4/QtNetwork
Qt LDFLAGS:
Qt libraries: -lQtGui -lQtNetwork -lQtCore -lqscintilla2
READLINE libraries: -lreadline
REGEX libraries: -lpcre
TERM libraries: -lncurses
UMFPACK CPPFLAGS:
UMFPACK LDFLAGS:
UMFPACK libraries:
X11 include flags:
X11 libraries: -lX11
Z CPPFLAGS:
Z LDFLAGS:
Z libraries: -lz
Default pager: less
gnuplot: gnuplot
Build Octave GUI: yes
JIT compiler for loops: no
Build Java interface: yes
Do internal array bounds checking: no
Use octave_allocator: no
Build static libraries: no
Build shared libraries: yes
Dynamic Linking: yes (dlopen)
Include support for GNU readline: yes
64-bit array dims and indexing: no
configure: WARNING: UMFPACK not found. This will result in some lack
of functionality for sparse matrices.
configure:
configure: NOTE: Libraries or auxiliary programs may be skippeimple d
if they are
configure: NOTE: not found OR if they are missing required features on your
configure: NOTE: system.
--------------------------- end snaps from configure output
-------------------------------------------------
When debugging we will use the following simple "image" as a test:
>> V = [ 1 0 0 0 0 0 1;
0 1 0 0 0 1 0;
0 1 0 0 0 1 0;
0 0 1 0 1 0 0;
0 0 1 0 1 0 0;
0 0 0 1 0 0 0;
0 0 0 1 0 0 0]
Now running ./run-octave -h &
>> VI = uint8(V)
>> class(VI)
ans = uint8
imshow(VI) ---- bombs!
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Inferior 1 (process 10826) exited with code 0177]
(gdb) bt
No stack.
what does the exit code 0177 mean?
Kjetil
On Thu, Oct 24, 2013 at 8:50 AM, c. <address@hidden> wrote:
>
> On 23 Oct 2013, at 23:09, Kjetil brinchmann Halvorsen <address@hidden> wrote:
>
>> Thanks!
>>
>> will try, but to include the error message is a bit diffficult when it
>> bombs, so there is never an error message to
>> see .... ¿Is there a way I can gwet to see the error message in such cases?
>>
>> Kjetil
>
> If you compiled Octave yourself you can start it using the script
> "run-octave" which is in the top level of the source tree.
> if you pass the option '-g' to 'run-octave' it will start the program in a
> debugger.
> When octace crashes you'll fall back to the debugger prompt, which you can
> use to gather more info about what happened.
> In particular you can use the command 'bt' (backtrace) to list the functions
> in the stack, that info is usually helpful
> when debugging this sort of problems.
>
> c.