GNU Octave uses the bug tracker at Savannah. There you can report a new bug, browse recent bugs, or search for bugs.

Guidelines for reporting a new bug

  1. Is the bug already known?

    If you your problem does not appear to be known, then you should report the problem.

  2. Is it really a bug?

    • If Octave crashes, for any input whatever, that is a bug. Reliable interpreters never crash.
    • If Octave produces incorrect results, for any input whatever, that is a bug.
    • If Octave produces an error message for valid input, that is a bug.
    • If Octave produces no error message for invalid input, that is a bug.

  3. Missing function in Octave

    • If the function is part of an Octave package, this is not a bug.
    • If the function exists in Matlab, but not in core Octave and not in an Octave package, that is a bug.

    It might take several months or years until for new features to become part of Octave, consider commercial support if you don’t want to wait that long).

  4. Make your bug report count

    • Report all the facts:
      Include all information that make it possible to fix the bug. If you are not sure whether to state a fact or leave it out, state it. This information includes your operating system, Octave version, exact error message or exact output.
    • Give a short, specific, complete example:
      Avoid: pseudocode, uninitialized variables, calls to unattached scripts or functions.
    • Justify your exectations briefly:
      Although it might seem obvious to you, someone examining the problem might not know what result you consider correct.

Sending Patches for Octave

If you have a suggested fix for a bug, please attach it to your report in the tracker. Your patch is more likely to be reviewed if you follow the guidelines from the Octave Wiki about the creation of changesets.