octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #47849] Documentation failing to build because


From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #47849] Documentation failing to build because of geometryimages.m
Date: Thu, 05 May 2016 03:37:44 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0

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

Ok, back from break.  Here's a quick summary of results that show printing
works for visible plots, but not non-visible plots:

FLTK


sebald@ ~/octave/octave/octave $ rm invisible.pdf
sebald@ ~/octave/octave/octave $
/usr/local/src/octave/octave/build1/run-octave -cli --silent
octave:1> graphics_toolkit ('fltk')
octave:2> sombrero
octave:3> print invisible.pdf
octave:4> print invisible.pdf
octave:5> figure visible off
octave:6> sombrero
octave:7> print invisible.pdf
error: __osmesa_print__: Depth and stencil doesn't match, are you sure you are
using OSMesa >= 9.0?
error: called from
    __opengl_print__ at line 172 column 7
    print at line 498 column 14
octave:7> print invisible.pdf
error: __osmesa_print__: Depth and stencil doesn't match, are you sure you are
using OSMesa >= 9.0?
error: called from
    __opengl_print__ at line 172 column 7
    print at line 498 column 14
octave:7> 
octave:7> 


Doesn't crash but has a stencil mismatch, so the instruction number doesn't
advance on of course no new invisible.pdf is created.  But invisible.pdf is
created on the visible invocation.

QT


>> graphics_toolkit ('qt')
>> sombrero
>> print invisible.pdf
>> print invisible.pdf
>> figure visible off
>> sombrero
>> print invisible.pdf


and at that point I hit return and the GUI disappears with the command line
result being "octave exited with signal 11".  As noted, Qt plots can freeze
the command line with "sombrero" or, I think, "print".  About 60% of the time
there seems to be a freeze somewhere in the above commands.

The freeze for Qt is probably a different issue.  Just interested in the crash
here.  I think this is at least an starting point for investigation, so I'll
take a look at this visibility and see if there is an
intialization/configuration bug.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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