From 0a1d263163f12502405b191895fffe48e47b2dfc Mon Sep 17 00:00:00 2001 From: simonmar Date: Tue, 13 Dec 2005 12:42:51 +0000 Subject: [PATCH] [project @ 2005-12-13 12:42:51 by simonmar] while I'm here, bring various other bits of this page up to date --- ghc/docs/users_guide/intro.xml | 53 ++++++++++++++++++++-------------------- 1 file changed, 27 insertions(+), 26 deletions(-) diff --git a/ghc/docs/users_guide/intro.xml b/ghc/docs/users_guide/intro.xml index 8d666ab..c384212 100644 --- a/ghc/docs/users_guide/intro.xml +++ b/ghc/docs/users_guide/intro.xml @@ -82,7 +82,9 @@ This list is for GHC users to chat among themselves. If you have a specific question about GHC, please check the - FAQ first (). + FAQ + first. @@ -244,18 +246,17 @@ How do I tell if I should report my bug? - Take a look at the FAQ () and Take a look at the FAQ and , which will give you some guidance as to whether the behaviour you're seeing is really a bug or not. If it is a bug, then it might have been reported before: - try searching the mailing list archives. The archives don't - have a built-in search facility, but we find that Google's site search works - pretty well: enter - site:www.haskell.org followed - by your search term into Google. + try searching on the bug tracker, + and failing that, try Google. If in doubt, just report it. @@ -271,44 +272,44 @@ What kind of machine are you running on, and exactly - what version of the operating system are you using? - (on a Unix system, uname -a or cat - /etc/motd will show the desired information.) + what version of the operating system are you using? (on a + Unix system, uname -a or cat + /etc/motd will show the desired information.) In + the bug tracker, this information can be given in the + “Architecture” and “Operating + system” fields. - What version of GCC are you using? gcc - -v will tell you. + What version of GCC are you using? gcc -v will tell you. - Run the sequence of compiles/runs that caused the - offending behaviour, capturing all the input/output in a - “script” (a UNIX command) or in an Emacs shell - window. We'd prefer to see the whole thing. + 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. - Be sure any Haskell compilations are run with a - (verbose) flag, so we can see exactly + Add the -v flag when running GHC, so we can see exactly what was run, what versions of things you have, etc. - What is the program behaviour that is wrong, in your + What is the program behaviour that is wrong, in your opinion? - If practical, please send enough source files for us - to duplicate the problem. + If practical, please attach or send enough source + files for us to duplicate the problem. - If you are a Hero and track down the problem in the - compilation-system sources, please send us patches relative - to a known released version of GHC, or whole files if you - prefer. + If you are a Hero and track down the problem in the + compilation-system sources, please send us patches (either + darcs send, plain patches, or just whole + files if you prefer). -- 1.7.10.4