 |
I've found a bug!
We know you're excited, but please avoid the urge to just email us! especially sending mail to Hernando or Nicholas directly. This includes sending us "Instant Messages" on the discourse section of the site. While you may prefer the privacy of a personal message, it's much quicker for you to write to the board, where you'll find all sorts of helpful people who are also often at all hours of the night. If you email us directly, we'll either not respond or just ask you to use the discourse board anyway.
We spend a lot of our time helping people with Wiring, so reading and following these instructions means that you respect our time and don't want to waste it.
First, read the FAQ. Start with digging through this page and maybe the platforms page too in case it's something specific to your operating system.
Second, search the bug report section in the discourse to see if your problem has already been reported. Most often, this will contain background on the bug, a workaround, or hopefully a bit about its status. The bug database is unfortunately incomplete so it doesn't cover everything, but it will get better with time.
If you don't find your bug, enter it as a new bug in the database, this will help us keep track of the issue.
When reporting please include information about
- the revision number (i.e. 0010)
- what operating system you're using, and on what kind of hardware
- a copy of the smallest possible piece of code that will produce the error you're having trouble with
- details of the error, either the red spew that you see in the console, or the last few lines from the files stdout.txt or stderr.txt from the 'lib' folder.
For stranger errors during compile time, you can also look inside the build folder which contains an intermediate (translated into C++) version of your code. The build folder will be located inside a temporary directory on your machine, probably /tmp/buildNNNN on Mac OS X and Linux, or on Windows, in one of its many "TEMP" folders, inside a buildNNNN folder (the Ns will be numbers or letters).
The more details you can post, the better, because it helps us figure out what's going on. Useful things when reporting:
- We want the minimum amount of code that will still replicate the bug. The worst that can happen is we get a report with a subject saying "problem!" along with a three page program. Sure, everyone likes a puzzle, but simpler code will receive a faster response.
- Occasionally we may need you to pack up a copy of your sketch folder or something similar so that we can try and replicate the weirdness on our own machine. Rest assured, we have no interest in messing with your fancy creations or stealing your ideas.
| |