[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #47699] FLTK can segfault after using copyobj
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #47699] FLTK can segfault after using copyobj |
Date: |
Fri, 22 Apr 2016 09:14:26 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 |
Follow-up Comment #1, bug #47699 (project octave):
Instead of title-bar clicking the segfault can be triggered by "close all" as
well.
Running it on Windows (both using the GUI and the BASH shell, mxe-octave
configured with "--enable-devel-tools"), I get this:
octave:1> graphics_toolkit fltk
octave:2> demo ("copyobj", 1)
copyobj example 1:
:
< demo commands >
:
copyobj example 1: failed
varargin(1): out of bound 0
{END}
I could track it a little bit by manually executing the demo commands (finally
invoking debug_on_error(1)), to a call to line.m
(copyobj.m L.87 -> struct2hdl.m L.144 -> struct2hdl.m.createline L.290 ->
line.m L.69)
where I think that just above that, in line.m L.56 the call to
__plt_get_axis_arg__ has reset varargin to empty. Why that happened is beyond
me; previous calls to line.m along this sequence in this demo all worked
well.
BTW in copyobj.m I see this syntax on L.52:
for hp = hparent(:)'
Is that valid syntax?
_______________________________________________________
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 <=
- [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, 2016/04/24
- [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