[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend |
Date: |
Sun, 24 Apr 2016 11:02:35 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 |
Update of bug #47699 (project octave):
Operating System: GNU/Linux => Any
_______________________________________________________
Follow-up Comment #8:
Rik, you suspected the legend. Running the example w/o the legend line makes
no difference here.
Then, maybe a red herring, but while experimenting with some graphics things
(polygon clipping) I hit a similar issue with the qt tookit after I tried
plotting a patch (really nothing more fancy than that) as follows:
figure
patch (opol{1}(:, 1), opol{1}(:, 2), 'c')
warning: opengl_renderer: x/y/zdata must have the same dimensions. Not
rendering.
## ...Indeed, no drawing
warning: opengl_renderer: x/y/zdata must have the same dimensions. Not
rendering.
## ^^^ that message ^^^ repeated over and over asynchronously
## in between other commands in the terminal
:
:
>> clear all; close all
warning: opengl_renderer: x/y/zdata must have the same dimensions. Not
rendering.
warning: called from
delete at line 58 column 3
closereq at line 42 column 5
close at line 96 column 5
>>
(opol.mat attached)
However, I couldn't reproduce it later on.
Apparently the graphics system is a bit unstable ATM.
Original bug reproducible on Windows as well => OS->Any
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?47699>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using copyobj, Rik, 2016/04/14
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using copyobj, Philip Nienhuis, 2016/04/22
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using copyobj, Rik, 2016/04/22
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend, Rik, 2016/04/22
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend, Philip Nienhuis, 2016/04/23
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend, Rik, 2016/04/23
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend, Rik, 2016/04/23
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend, Lachlan Andrew, 2016/04/24
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend,
Philip Nienhuis <=
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend, Philip Nienhuis, 2016/04/24
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend, Lachlan Andrew, 2016/04/24
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend, Lachlan Andrew, 2016/04/24
- Message not available
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend, Philip Nienhuis, 2016/04/24
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend, Lachlan Andrew, 2016/04/24
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend, Juan Pablo Carbajal, 2016/04/27
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend, Juan Pablo Carbajal, 2016/04/27
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend, Lachlan Andrew, 2016/04/27
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend, Lachlan Andrew, 2016/04/27
- [Octave-bug-tracker] [bug #47699] FLTK can segfault after using legend, Rik, 2016/04/27