|
| 1 | +--- |
| 2 | +title: Bug reports |
| 3 | +sidebar: false |
| 4 | +--- |
| 5 | + |
| 6 | +**Please help us by reporting any problems you find.** |
| 7 | + |
| 8 | +NumPy and SciPy libraries make use of GitHub to do project management. |
| 9 | +There, you can see what we are currently working on (Pull Requests), as |
| 10 | +well as file bug-reports (issues). |
| 11 | + |
| 12 | +1. Go to the relevant page: |
| 13 | + - [SciPy library pull |
| 14 | + requests](https://github.com/scipy/scipy/pulls) |
| 15 | + - [SciPy library bug |
| 16 | + reports](https://github.com/scipy/scipy/issues) |
| 17 | + - [NumPy library pull |
| 18 | + requests](https://github.com/numpy/numpy/pulls) |
| 19 | + - [NumPy library bug |
| 20 | + reports](https://github.com/numpy/numpy/issues) |
| 21 | +2. On GitHub, you need to register an account the first time you use |
| 22 | + it. |
| 23 | +3. Make sure the bug hasn\'t already been reported. Click on \"Search\" |
| 24 | + and type in some keywords to search for. |
| 25 | +4. File your bug-report by clicking \"New Issue\" on GitHub. For advice |
| 26 | + on how to provide a useful bug report, see the |
| 27 | + [guidelines for submitting bugs](#guidelines-for-submitting-bugs). |
| 28 | +5. Note that the bug trackers are mostly for actual bugs. If you want |
| 29 | + to propose an enhancement, then the mailing list is a better place |
| 30 | + to get feedback. |
| 31 | + |
| 32 | +**Thank you for helping to make** SciPy **better!** |
| 33 | + |
| 34 | +# Guidelines for submitting bugs |
| 35 | + |
| 36 | +- Provide a good description. Tickets in the vein of \"SciPy is |
| 37 | + BROKEN!!!\" are not useful; rather, please state the problem |
| 38 | + clearly, e.g., \"scipy.ndimage ignores keyword \'axis\'\". |
| 39 | + |
| 40 | +- Include a minimal standalone code snippet to illustrate the problem. |
| 41 | + Try to narrow it down to a few lines. |
| 42 | + |
| 43 | +- If you experience segfaults or memory errors, give a GDB traceback: |
| 44 | + |
| 45 | + $ gdb python |
| 46 | + GNU gdb 6.3.50-20050815 (Apple version gdb-573) (Fri Oct 20 15:50:43 GMT 2006) |
| 47 | + Copyright 2004 Free Software Foundation, Inc. |
| 48 | + GDB is free software, covered by the GNU General Public License, and you are |
| 49 | + welcome to change it and/or distribute copies of it under certain conditions. |
| 50 | + Type "show copying" to see the conditions. |
| 51 | + There is absolutely no warranty for GDB. Type "show warranty" for details. |
| 52 | + This GDB was configured as "i386-apple-darwin"...Reading symbols for shared |
| 53 | + libraries .. done |
| 54 | + (gdb) run -c "import scipy; scipy.test(10,10)" |
| 55 | + Starting program: /usr/local/bin/python -c "import scipy; scipy.test()" |
| 56 | + Reading symbols for shared libraries . done |
| 57 | + Program received signal SIGTRAP, Trace/breakpoint trap. |
| 58 | + 0x8fe01010 in __dyld__dyld_start () |
| 59 | + (gdb) c |
| 60 | + Continuing. |
| 61 | + Reading symbols for shared libraries . done |
| 62 | + Reading symbols for shared libraries . done |
| 63 | + ... |
| 64 | + |
| 65 | + Then use the \"bt\" command after the segfault happens to get the |
| 66 | + backtrace. Alternatively, run the code using |
| 67 | + [Valgrind](http://valgrind.org/). |
0 commit comments