Changes between Version 13 and Version 14 of ReportABug


Ignore:
Timestamp:
May 24, 2011 7:34:17 PM (4 years ago)
Author:
simonmar
Comment:

details about reporting RTS failures

Legend:

Unmodified
Added
Removed
Modified
  • ReportABug

    v13 v14  
    1616Take 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. 
    1717 
    18 If it is a bug, then it might have been reported before: try searching on the [http://hackage.haskell.org/trac/ghc bug tracker], and failing that, try [http://www.google.com/ Google]. 
     18'''If you encounter a crash from the runtime system''', which usually manifest as one of the following error messages: 
    1919 
    20 If in doubt, just report it. 
     20{{{ 
     21internal error: evacuate: strange closure type ... 
     22internal error: scavenge: unimplemented/strange closure type ... 
     23internal error: update_fwd: unknown/strange object ... 
     24}}} 
    2125 
    22 == If already reported, vote for it! == 
     26then 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. 
    2327 
    24 If someone else has already reported the bug you've found, 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. 
     28Otherwise, 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]. 
    2529 
    26 Use a comma or space (but not semicolon) to separate your email address from the next one. 
     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'''. 
    2733 
    2834== What to put in a bug report ==