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

[Liang Tang]

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

Hi Arun, 

I did try to read the files you sent yesterday evening.  But I don't have the
ability to understand the traces you provided.  

I do have two questions: 

(1) I assume that Qt is a 3rd party library. Correct?  If yes, is there a
feasible mean to debug this issue w/o vendor involvement? 
(2) From what I know in the distant past, crash mostly came from two sources:
code error or corrupted memory.  Based on your observation, which one is more
likely? 

I attach another m file to reflect what I know from the comments you post. 
The intention is to further simplify the test case. If it introduce more
confusion, we don't need to use it.   

Using test_crash_submit_1([],[],7)  will not crash.  But cut/paste the
associated lines, including the function definitions, into the command window,
crashed 100% of time for me.  

The outcome from case 4 vs 5 is also surprising to me.  

Thanks,


(file #54008)

    _______________________________________________________

Additional Item Attachment:

File name: test_crash_submit_1.m          Size:10 KB
    <https://file.savannah.gnu.org/file/test_crash_submit_1.m?file_id=54008>



    _______________________________________________________

Reply to this item at:

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

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