Has anybody tried to compile octplot for Debian testing.
Compiling the code goes well. I.e
./configure
make
make install
All completes. However octave crashes
when I use octplot. The plot
window appears with the plot in it
and then octave crashes. The plot
window stays open and can be re-sized
however it starts to misbehave as soon
as I click on it using the mouse.
octave:1> toggle_octplot
octave:2> line_demo
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
octave:3> panic: Segmentation fault -- stopping myself...
attempting to save variables to `octave-core'...
save to `octave-core' complete
Segmentation fault
Octave version :
---------------------
GNU Octave, version 2.1.71 (i486-pc-linux-gnu).
2.1.71-5 Debian pakage.
octplot version
--------------------
octplot-0.2.61
Compiler used to compile.
----------------------------------
> g++ -v
yhis has been discussed on the octave-help lists and it is probably caused by a bug in gcc-4/libstdc++. To overcome this bug, try running octave with the GLIBCXX_FORCE_NEW environment var set to one:
instead of
octave
use:
GLIBCXX_FORCE_NEW=1 octave
Tell me if it works
Shai
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear OctPlot list,
Has anybody tried to compile octplot for Debian testing.
Compiling the code goes well. I.e
./configure
make
make install
All completes. However octave crashes
when I use octplot. The plot
window appears with the plot in it
and then octave crashes. The plot
window stays open and can be re-sized
however it starts to misbehave as soon
as I click on it using the mouse.
octave:1> toggle_octplot
octave:2> line_demo
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
ans = 2
octave:3> panic: Segmentation fault -- stopping myself...
attempting to save variables to `octave-core'...
save to `octave-core' complete
Segmentation fault
Octave version :
---------------------
GNU Octave, version 2.1.71 (i486-pc-linux-gnu).
2.1.71-5 Debian pakage.
octplot version
--------------------
octplot-0.2.61
Compiler used to compile.
----------------------------------
> g++ -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --enable-languages=c,c++,java,f95,objc,ada, treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --program-suffix= -4.0 --enable-__cxa_atexit --enable-libstdcxx-allocator=mt --enable-clocale=gnu --enable-libstdcxx-debug --enable-java-gc=boehm --enable-java-awt=gtk --enable-g tk-cairo --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-4.0-1.4.2.0/jre --enable-m pfr --disable-werror --enable-checking=release i486-linux-gnu
Thread model: posix
gcc version 4.0.2 (Debian 4.0.2-2)
`mkoctfile -p CXX` -v
Same as above.
Peter Jensen
Peter,
I don't have a clue :(
Can yu please try running octave with gdb to get a trace?:
gdb octave
run
toggle_octplot
line_demo
...
when it crashes you should get the gdb prompt, type:
bt
and send me the output.
BTW, maybe it will be worthwhile to send the output to the octave-help list also -- maybe someone there will have a clue
Thanks for helping
Shai
OK,
yhis has been discussed on the octave-help lists and it is probably caused by a bug in gcc-4/libstdc++. To overcome this bug, try running octave with the GLIBCXX_FORCE_NEW environment var set to one:
instead of
octave
use:
GLIBCXX_FORCE_NEW=1 octave
Tell me if it works
Shai