[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-task-tracker] [task #11142] Decide on whether to fix bug #32683,
From: |
Rik |
Subject: |
[Octave-task-tracker] [task #11142] Decide on whether to fix bug #32683, incorrect ndarray concatenation |
Date: |
Mon, 16 May 2011 02:53:54 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 |
URL:
<http://savannah.gnu.org/task/?11142>
Summary: Decide on whether to fix bug #32683, incorrect
ndarray concatenation
Project: GNU Octave
Submitted by: rik5
Submitted on: Sun 15 May 2011 07:53:53 PM PDT
Should Start On: Sun 15 May 2011 12:00:00 AM PDT
Should be Finished on: Tue 31 May 2011 12:00:00 AM PDT
Category: None
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Fixed Release: None
Planned Release: None
_______________________________________________________
Details:
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.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/task/?11142>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-task-tracker] [task #11142] Decide on whether to fix bug #32683, incorrect ndarray concatenation,
Rik <=