... | ... | @@ -49,7 +49,7 @@ Here is a check-list of things to cover in your description: |
|
|
1. The source code of the program that shows the bug. You can give the code inline, or attach a file, or attach a tarball.
|
|
|
1. What is the program behaviour that is wrong, in your opinion?
|
|
|
1. (Only if you think the bug is platform dependent): What kind of machine are you running on, and exactly what version of the operating system are you using? On a Unix-like system, `uname -a` and `cat /etc/motd` will show the desired information. In the bug tracker, this information can be given in the "Architecture" and "Operating system" fields.
|
|
|
1. What version of GCC are you using? `gcc -v` will tell you.
|
|
|
1. What version of your C compiler are you using? `cc -v` will tell you.
|
|
|
1. Run the sequence of compiles/runs that caused the offending behaviour, cut-and-paste the whole session into the bug report. We'd prefer to see the whole thing.
|
|
|
1. Add the `-v` flag when running GHC, so we can see exactly what was run, what versions of things you have, etc. When using `cabal-install` this can be done using the `--ghc-options=-v` flag or by adding a similar field to your `cabal.project` file.
|
|
|
1. Add the `-dcore-lint` flag when running GHC. This adds some significant internal consistency-checking, which often nails bugs early.
|
... | ... | |