[Octave-bug-tracker] [bug #63388] Octave may crash with uitable containing true/false data

[Arun Giridhar]

Follow-up Comment #13, bug #63388 (project octave):

After tracing it through set() in graphics.cc, I can't see anything that
Octave should do differently. All the cases pass through the very last
else-block in the big if-else ladder (Case V in the attached diagoostics
diff). All that else block does is splice in the new argument to the argument
list, and request a redraw through the local variable drawnow_requested, which
in turn triggers a redraw through Vdrawnow_requested.

The bug does seem to be inside Qt as dasergatskov said. It seems to have
trouble with constructing and destroying a checkbox in certain circumstances,
such as replacing it with another widget like a string or a number.

Attaching a patch to add cout statements to graphics.cc, if anyone wants to
trace the diagnostics.

(file #53979)

    _______________________________________________________

Additional Item Attachment:

File name: set_diagnostics.patch          Size:3 KB
    <https://file.savannah.gnu.org/file/set_diagnostics.patch?file_id=53979>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63388>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/