bugGNU Octave - Bugs: bug #55047, Running the test suite causes...

 
 

bug #55047: Running the test suite causes Octave to segfault on Windows

Submitted by:  Markus Mützel <mmuetzel>
Submitted on:  Sun 18 Nov 2018 02:02:38 PM UTC  
 
Category:  None Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Segfault, Bus Error, etc.
Status:  Confirmed Assigned to:  None
Originator Name:  Open/Closed:  Open
Release:  dev Operating System:  Microsoft Windows

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Fri 30 Nov 2018 10:08:56 PM UTC, comment #2:

Just as a info point, if I change runtestsuit to run the fixed tests before the integrated tests, it does not crash.

John Donoghue <lostbard>
Project Member
Sun 18 Nov 2018 05:00:16 PM UTC, comment #1:

On my 64-bit Windows 7 Professional box and Windows 7 Enterprise box at work, _run_test_suite_ segfaults in the fixed tests section, and fntests.log always ends with the colormap test.

Insofar it is consistent on just my boxes and ends elsewhere on other people's boxes I can't say. What might matter there is that I have several binary patches in my cross-builds (h5read, uitable, matrix right division, shortcut keys for variable editor).

The individual tests run fine (cd-ing to the fixed test dir and running them one by one (using "test <blabla>.tst").
I also tried running just the fixed tests:
_run_test_suite ({}, {'/path/to/fixed/tests'}, {})
and also then I saw no segfault.
Echo of screen messages attached.
Because of that I didn't pay much attention, but I agree with Markus that _run_test_suite_ shouldn't end in a segfault.

Maybe the amount of tests, or amount of some type(s) of tests, induces oversaturation of Octave's resources somewhere?

(file #45482)

Philip Nienhuis <philipnienhuis>
Project Member
Sun 18 Nov 2018 02:02:38 PM UTC, original submission:

When executing "__run_test_suite__" with Octave from the default branch on Windows causes it to crash with a segmentation fault. See the attached backtraces.
The crash happens at the fixed tests towards the end of the test suite at different tests that seem to be unrelated. But the backtraces look similar.

The last version that completes the test suite without crashing is hg id a0079f6f8c4 with 466c405ee09b and ac0b3c09c3db grafted on top.
I am having trouble cross-compiling a lot of the sub-sequent nodes for Windows. The next version I managed to cross-compile is hg id 14e844f1459a. That version already shows the segfault.

So this leaves a window of ~25 changesets starting with:

And ending with:

Markus Mützel <mmuetzel>
Project Member

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by lostbard (Posted a comment)
  • -email is unavailable- added by philipnienhuis
  • -email is unavailable- added by mmuetzel (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

     

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-11-18 philipnienhuis Carbon-Copy- => Added philipnienhuis
    2018-11-18 philipnienhuis StatusNone => Confirmed
    2018-11-18 philipnienhuis Attached File- => Added one_single_and_fixed_tests_bug_55047.txt, #45482
    2018-11-18 mmuetzel Attached File- => Added gdb_log_e5acf1d94d33.txt, #45477
        Attached File- => Added gdb_log_e142769913f8.txt, #45478

    Back to the top


    Powered by Savane 3.3