[Octave-bug-tracker] [bug #47849] Documentation failing to build because of geometryimages.m

[Dan Sebald]

Follow-up Comment #1, bug #47849 (project octave):

I've tried the following:


./run-octave -cli -g --path
/home/sebald/octave/octave/octave/doc/interpreter/


and FLTK becomes the default.  It behaves similar to what I described in the
previous post.  I'll instead do


./run-octave -g --no-gui --path
/home/sebald/octave/octave/octave/doc/interpreter/


I'm not seeing much:


>> graphics_toolkit('qt');
>> geometryimages ('doc/interpreter/', 'griddata', 'eps');
>> geometryimages ('doc/interpreter/', 'griddata', 'eps');

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdb529700 (LWP 25604)]
0x00007ffff33f77e9 in glGetIntegerv () from /usr/lib/nvidia-340/libGL.so.1


probably because there is no traceable code for the video driver.  "dump",
"trace"?  Is there something more I can do here?

Anyway, because of the fact all three graphics toolkits are acting strange
under the same commands, my guess is the issue might lie in Octave script or
plot-related C code.  The seg fault above is probably because of improper data
fed to a GL function.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47849>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/