taskGNU Octave - Tasks: task #11142, Decide on whether to fix bug...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

task #11142: Decide on whether to fix bug #32683, incorrect ndarray concatenation

Submitter:  Rik <rik5>
Submitted:  Mon 16 May 2011 02:53:53 AM UTC
   
 
Should Start On:  Sun 15 May 2011 07:00:00 AM UTC Should be Finished on:  Tue 31 May 2011 07:00:00 AM UTC
Category:  None Priority:  5 - Normal
Status:  Cancelled Privacy:  Public
Assigned to:  None Originator Name: 
Open/Closed:  Closed Fixed Release:  None
Planned Release:  None

Mon 06 Jun 2011 07:56:35 PM UTC, comment #2: 

It was closed because I decided it was no longer a gating item for having a 3.4.1 release. 

The bug in question definitely needs to be fixed.  But, there have been no reports of segmentation faults so it is only causing incorrect behavior and not crashes.  And we don't require all incorrect behavior bugs to be solved before issuing a new release.

Rik <rik5>
Group administrator
Mon 06 Jun 2011 07:44:55 PM UTC, comment #1: 

Why was this task cancelled and closed?

John W. Eaton <jwe>
Group administrator
Mon 16 May 2011 02:53:53 AM UTC, original submission:  

Octave appears to be sampling uninitialized memory in bug #32683.  There are no reports of segmentation faults, but this might be masking something deeper.  In any case, it is a regression from 3.2.4 which behaved correctly for the simple case of array concatenation ([A ; B]).

My vote would be to at least do a quick perusal for understanding.  If the bug cannot lead to a segfault then it can be fixed later and needn't hold up the 3.4.1 release.

Rik <rik5>
Group administrator

 

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

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by rik5 (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2011-05-25 rik5 Open/ClosedOpen Closed
    2011-05-25 rik5 StatusNone Cancelled

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code