octave-maintainers
[Top][All Lists]
Advanced

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

Re: Build error: __init_fltk__ missing


From: Michael Godfrey
Subject: Re: Build error: __init_fltk__ missing
Date: Fri, 06 Nov 2009 14:25:13 +0100
User-agent: Thunderbird 2.0.0.23 (X11/20090817)

I tried ./run-octave -g and got:

Program received signal SIGSEGV, Segmentation fault.
0x000000396727f440 in ?? () from /usr/lib64/nvidia/libGL.so.1
Missing separate debuginfos, use: debuginfo-install
arpack-2.1-11.fc11.x86_64 atlas-3.8.3-9.fc11.x86_64
blas-3.2.1-3.fc11.x86_64 expat-2.0.1-6.fc11.1.x86_64
fftw-3.2.1-2.fc11.x86_64 fltk-1.1.9-4.fc11.x86_64
fontconfig-2.7.1-1.fc11.x86_64 freetype-2.3.9-5.fc11.x86_64
ftgl-2.1.2-10.fc11.x86_64 glibc-2.10.1-5.x86_64 hdf5-1.8.3-1.fc11.x86_64
libX11-1.2.2-1.fc11.x86_64 libXau-1.0.4-5.fc11.x86_64
libXcursor-1.1.9-4.fc11.x86_64 libXext-1.0.99.1-3.fc11.x86_64
libXfixes-4.0.3-5.fc11.x86_64 libXft-2.1.13-2.fc11.x86_64
libXinerama-1.0.3-4.fc11.x86_64 libXrender-0.9.4-5.fc11.x86_64
libgcc-4.4.1-2.fc11.x86_64 libgfortran-4.4.1-2.fc11.x86_64
libstdc++-4.4.1-2.fc11.x86_64 libxcb-1.2-4.fc11.x86_64
mesa-libGLU-7.6-0.1.fc11.x86_64 ncurses-libs-5.7-2.20090207.fc11.x86_64
pcre-7.8-2.fc11.x86_64 readline-5.2-14.fc11.x86_64
suitesparse-3.2.0-6.fc11.x86_64 zlib-1.2.3-22.fc11.x86_64
(gdb) bt
#0  0x000000396727f440 in ?? () from /usr/lib64/nvidia/libGL.so.1
#1  0x00000039672704e5 in _fini () from /usr/lib64/nvidia/libGL.so.1
#2  0x0000003ed5a0f0cc in _dl_fini () from /lib64/ld-linux-x86-64.so.2
#3  0x0000003ed5e367f2 in exit () from /lib64/libc.so.6
#4  0x00007ffff75e90f8 in clean_up_and_exit (retval=0) at toplev.cc:679
#5  0x00007ffff75e9727 in main_loop () at toplev.cc:626
#6  0x00007ffff759728d in octave_main (argc=<value optimized out>,
argv=0x7fffffffcc58,
    embedded=<value optimized out>) at octave.cc:887
#7  0x0000003ed5e1ea2d in __libc_start_main () from /lib64/libc.so.6
#8  0x00000000004007c9 in _start ()
(gdb)
================================================
This appears to be specific to nvidia driver, so it probably does not
deserve high priority.  However, some recent change has caused this.
This happens even if I close the plot window before "quit."



reply via email to

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