Changes between Version 16 and Version 17 of ReportABug


Ignore:
Timestamp:
Dec 30, 2012 7:28:51 PM (3 years ago)
Author:
simonpj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReportABug

    v16 v17  
    1313== How do I tell if I should report my bug? ==
    1414
    15 Take a look at the [http://haskell.org/haskellwiki/GHC/FAQ FAQ] and [http://www.haskell.org/ghc/docs/latest/html/users_guide/wrong.html Chapter 9, What to do when something goes wrong], which will give you some guidance as to whether the behaviour you're seeing is really a bug or not.
     15 * Take a look at the [http://haskell.org/haskellwiki/GHC/FAQ FAQ] and [http://www.haskell.org/ghc/docs/latest/html/users_guide/wrong.html Chapter 9, What to do when something goes wrong], which will give you some guidance as to whether the behaviour you're seeing is really a bug or not.
    1616
    17 '''If you encounter a crash from the runtime system''', which usually manifest as one of the following error messages:
     17 * Please search for existing tickets on the [http://hackage.haskell.org/trac/ghc bug tracker] or [http://www.google.com/?q=site:hackage.haskell.org/trac/ghc/ticket%20 Google].  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. 
    1818
     19 * If you do find an existing ticket that seems to describe the same problem, then
     20    * Add a comment that explains how it manifests for you, and add your description of how to reproduce it (see below)
     21    * Add yourself to the CC list for the bug. We will try to prioritise bugs that affect a lot of people, and the length of the CC list is how we are currently determining this.  Use a comma or space (but not semicolon) to separate your email address from the next one.
     22
     23 * However, if you encounter a crash from the runtime system, then don't bother searching for existing tickets - '''just create a new ticket'''.  These indicate a general RTS failure of some kind, and can arise due to a wide range of causes, so it is easier for us to track each failure in a separate ticket. 
     24
     25 Runtime system errors usually manifest as one of the following error messages:
    1926{{{
    2027internal error: evacuate: strange closure type ...
     
    2431}}}
    2532
    26 then don't bother searching for existing tickets - '''just create a new ticket'''.  These indicate a general RTS failure of some kind, and can arise due to a wide range of causes, so it is easier for us to track each failure in a separate ticket.
    27 
    28 Otherwise, try searching for existing tickets on the [http://hackage.haskell.org/trac/ghc bug tracker] or [http://www.google.com/?q=site:hackage.haskell.org/trac/ghc/ticket%20 Google].
    29 
    30 '''If you find an existing ticket''' that seems to describe the same problem, then '''add yourself to the CC list''' for the bug. We will try to prioritise bugs that affect a lot of people, and the length of the CC list is how we are currently determining this.  Use a comma or space (but not semicolon) to separate your email address from the next one.
    31 
    32 '''If in doubt, just report your bug'''.
     33 * '''If in doubt, just report your bug'''.
    3334
    3435== What to put in a bug report ==