| ... | ... | @@ -11,14 +11,16 @@ 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
|
|
|
|
- Register an account on this GitLab instance.
|
|
|
|
- **Ask for your account to be approved**. This is an unfortunate workaround for all the spam that the service attracts.
|
|
|
|
- Contact admins through [the mailing list or IRC](https://gitlab.haskell.org/ghc/ghc/-/wikis/mailing-lists-and-irc).
|
|
|
|
- Create a [new bug](https://gitlab.haskell.org/ghc/ghc/issues), and enter your bug report. Make a new ticket for your bug unless you are 100% sure there is a ticket for your exact problem.
|
|
|
|
|
|
|
|
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).
|
|
|
|
|
|
|
|
## 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.
|
|
|
|
- **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.
|
|
|
|
|
|
|
|
- **Duplicate bug reports**. Please search for existing tickets on the [bug tracker](https://gitlab.haskell.org/ghc/ghc/issues). If your problem has already been reported, it saves time to have all the manifestations of the same bug gathered together. If you get an error message from GHC, a good search key is usually the non-program-specific part of the error message.
|
|
|
|
|
| ... | ... | |
