|
|
# Reporting bugs in GHC
|
|
|
|
|
|
---
|
|
|
|
|
|
See also [Issue conventions](https://gitlab.haskell.org/ghc/ghc/wikis/gitlab/issues)
|
|
|
|
|
|
---
|
|
|
|
|
|
GHC is a changing system so there are sure to be bugs in it.
|
|
|
|
|
|
|
|
|
To report a bug:
|
|
|
|
|
|
- Register an account on this GitLab instance.
|
... | ... | @@ -18,6 +11,9 @@ To report a bug: |
|
|
|
|
|
If you believe that your bug may have security implications please refer to GHC's [Security Disclosure Policy](https://www.haskell.org/ghc/disclosures.html).
|
|
|
|
|
|
For more information about how GHC's developers handle bugs, see [Issue conventions](https://gitlab.haskell.org/ghc/ghc/wikis/gitlab/issues).
|
|
|
|
|
|
|
|
|
## 1. How do I tell if I should report my bug?
|
|
|
|
|
|
- **Is it a bug at all?** Take a look at ["What to do when something goes wrong"](http://www.haskell.org/ghc/docs/latest/html/users_guide/gone_wrong.html) from the GHC User's Guide, which will give you some guidance as to whether the behaviour you're seeing is really a bug or not.
|
... | ... | @@ -45,6 +41,7 @@ If you believe that your bug may have security implications please refer to GHC' |
|
|
|
|
|
- **If in doubt, just report your bug**.
|
|
|
|
|
|
|
|
|
## 2. What to put in a bug report
|
|
|
|
|
|
The name of the bug-reporting game is: facts, facts, facts. Don't omit them because "Oh, they won't be interested…".
|
... | ... | |