[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #42825] Memory corruption in sparse matrix ope
|
From: |
Lachlan Andrew |
|
Subject: |
[Octave-bug-tracker] [bug #42825] Memory corruption in sparse matrix operation |
|
Date: |
Tue, 12 Jan 2016 00:19:20 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0 |
Follow-up Comment #6, bug #42825 (project octave):
Michael, I've realised part of the problem. If a person is submitting, say, a
GUI bug, they need to select one from "item group", and there is no option
that simply says "unexpected behaviour", so they are forced to select
"incorrect result".
Would it be possible to split "incorrect result" into "unexpected behaviour"
and "wrong answer", or to find some other way to search on only numerical
"incorrect result" bugs?
An alternative would be for a core developer to assign priorities to bugs --
currently most have the default priority, and casual developers like me can't
change that.
Should we move this to the developers mailing list?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?42825>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/