Mercurial > web-octave
comparison pages/menu/bugs.md @ 217:6de5c7dcc43f
maint: add "pages/menu" subfolder to get a better overview.
Pages in this folder have a menu entry at the top bar of the website.
| author | Kai T. Ohlhus <k.ohlhus@gmail.com> |
|---|---|
| date | Tue, 15 Sep 2020 14:55:06 +0900 |
| parents | |
| children | 9057b6832c9a |
comparison
equal
deleted
inserted
replaced
| 216:c8126c010d67 | 217:6de5c7dcc43f |
|---|---|
| 1 --- | |
| 2 layout: page | |
| 3 title: Bugs | |
| 4 menu: true | |
| 5 permalink: bugs | |
| 6 --- | |
| 7 | |
| 8 GNU Octave uses the bug tracker at [Savannah]({{ site.bugs_url }}). | |
| 9 There you can [report a new bug]({{ site.bugs_url }}&func=additem), | |
| 10 [browse recent bugs]({{ site.bugs_url }}), | |
| 11 or [search for bugs]({{ site.bugs_url }}&func=search). | |
| 12 | |
| 13 ### Guidelines for reporting a new bug | |
| 14 | |
| 15 1. **Is the bug already known?** | |
| 16 | |
| 17 - [Search for already reported bugs at the bug tracker]({{ site.bugs_url }}&func=search), | |
| 18 - look at the | |
| 19 [list of known causes of trouble]({{ site.docs_url }}/Trouble.html) | |
| 20 in the Octave manual. | |
| 21 | |
| 22 <p></p> | |
| 23 | |
| 24 If you your problem **does not appear** to be known, | |
| 25 then you should report the problem. | |
| 26 | |
| 27 2. **Is it really a bug?** | |
| 28 | |
| 29 - If Octave **crashes**, for any input whatever, that is a bug. | |
| 30 Reliable interpreters never crash. | |
| 31 - If Octave produces **incorrect results**, for any input whatever, | |
| 32 that is a bug. | |
| 33 - If Octave produces an **error message** for **valid input**, that is a bug. | |
| 34 - If Octave produces **no error message** for **invalid input**, | |
| 35 that is a bug. | |
| 36 | |
| 37 <p></p> | |
| 38 | |
| 39 3. **Missing function in Octave** | |
| 40 | |
| 41 - If the function is | |
| 42 [part of some Octave Forge package]({{ site.sourceforge_url }}/functions_by_alpha.php), | |
| 43 this is **not** a bug. | |
| 44 - If the function **exists in Matlab**, | |
| 45 but **not in core Octave** and **not in Octave Forge packages**, | |
| 46 that is a bug. | |
| 47 | |
| 48 <p></p> | |
| 49 | |
| 50 It might take several months or years until for new features to become part | |
| 51 of Octave, consider | |
| 52 [commercial support]({{ "commercial-support.html" | relative_url }}) | |
| 53 if you don't want to wait that long). | |
| 54 | |
| 55 4. **Make your bug report count** | |
| 56 | |
| 57 - **Report all the facts:**<br> | |
| 58 Include all information that make it possible to fix the bug. | |
| 59 If you are not sure whether to state a fact or leave it out, state it. | |
| 60 This information includes your **operating system**, **Octave version**, | |
| 61 **exact error message** or **exact output**. | |
| 62 - **Give a short, specific, complete example:**<br> | |
| 63 Avoid: pseudocode, uninitialized variables, | |
| 64 calls to unattached scripts or functions. | |
| 65 - **Justify your exectations briefly:**<br> | |
| 66 Although it might seem obvious to you, | |
| 67 someone examining the problem might not know what result you consider | |
| 68 correct. | |
| 69 | |
| 70 | |
| 71 ### Sending Patches for Octave | |
| 72 | |
| 73 If you have a suggested fix for a bug, | |
| 74 please attach it to your report in the tracker. | |
| 75 Your patch is more likely to be reviewed if you follow the guidelines from the | |
| 76 Octave Wiki about the [creation of changesets]({{ site.wiki_url }}/Mercurial). |