[Octave-bug-tracker] [bug #42825] Memory corruption in sparse matrix operation

[Lachlan Andrew]

Follow-up Comment #5, bug #42825 (project octave):

Michael, it seems not to be clear enough.

I interpret "incorrect result" as a "gross numerical error", but browsing the
bugs that have that type shows that others interpret it to mean "it didn't do
what I expected", including "command window blank", "gripe error appearing",
"unable to create classes", "need better configure test" etc.

What is worse is that this bug (clearly an "incorrect result") was (also
correctly) labelled as "regression".  That label is useful for identifying the
cause of the bug, but not for selecting which bugs to fix.  It would be nice
to be able to mark a bug as both "wrong number" and "regression".

I'm starting a wiki page [http://wiki.octave.org/Status_of_bugs] where I'm
recommending changes to the status etc of groups.  Perhaps I'll start
recommending reclassification of "incorrect result" bugs once I've gone
through all the "patch submitted" bugs :)

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?42825>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/