X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=ghc%2Fdocs%2Fusers_guide%2Fgone_wrong.sgml;h=9467460f492fc3d5777735c53b5acb8afb6d43b2;hb=e5e322e92a0d0a2f8aef7da79c45b12eaa6e000b;hp=b5910c9960e08646ed9c8b3a2f1f6da3d9157e3e;hpb=9aef6bea5fa5508653d10c129cac88ea39439828;p=ghc-hetmet.git
diff --git a/ghc/docs/users_guide/gone_wrong.sgml b/ghc/docs/users_guide/gone_wrong.sgml
index b5910c9..9467460 100644
--- a/ghc/docs/users_guide/gone_wrong.sgml
+++ b/ghc/docs/users_guide/gone_wrong.sgml
@@ -315,7 +315,8 @@ exception (please report it if it does).
Glasgow Haskell is a changing system so there are sure to be bugs in
-it. Please report them to glasgow-haskell-bugs@haskell.org! (However, please
+it. Please report them to
+glasgow-haskell-bugs@haskell.org! (However, please
check the earlier part of this section to be sure it's not a known
not-really-a problem.)
@@ -331,9 +332,9 @@ Don't omit them because “Oh, they won't be interested…”
- What kind of machine are you running on, and exactly what
-version of the operating system are you using? (uname -a or cat
-/etc/motd will show the desired information.)
+What kind of machine are you running on, and exactly what version of
+the operating system are you using? (uname -a or
+cat /etc/motd will show the desired information.)
@@ -373,8 +374,8 @@ have, etc.
- If practical, please send enough source files/interface files
-for us to duplicate the problem.
+ If practical, please send enough source files for us to duplicate the
+ problem.
@@ -434,9 +435,9 @@ it probably is a GC bug.
-If it crashes with the normal
-collector, but not when you force two-space collection (
-runtime flag), then it probably is a GC bug.
+If it crashes with the normal collector, but not when you force
+two-space collection ( runtime flag), then it
+probably is a GC bug.
@@ -445,9 +446,9 @@ runtime flag), then it probably is a GC bug.
-If it is a GC bug, you may be able to avoid it by using a
-particular heap size or by using a runtime flag. (But don't
-forget to report the bug!!!)
+If it is a GC bug, you may be able to avoid it by
+using a particular heap size or by using a
+runtime flag. (But don't forget to report the bug!!!)