From e5e322e92a0d0a2f8aef7da79c45b12eaa6e000b Mon Sep 17 00:00:00 2001 From: simonmar Date: Mon, 3 Apr 2000 12:47:57 +0000 Subject: [PATCH] [project @ 2000-04-03 12:47:08 by simonmar] don't mention non-existent RTS options. --- ghc/docs/users_guide/gone_wrong.sgml | 25 +++++++++++++------------ ghc/docs/users_guide/sooner.sgml | 26 ++++++++++++++------------ 2 files changed, 27 insertions(+), 24 deletions(-) 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!!!) diff --git a/ghc/docs/users_guide/sooner.sgml b/ghc/docs/users_guide/sooner.sgml index dd38339..e7cae66 100644 --- a/ghc/docs/users_guide/sooner.sgml +++ b/ghc/docs/users_guide/sooner.sgml @@ -120,11 +120,10 @@ to correct it. -The parts of the compiler that seem most prone to wandering off for a -long time are the abstract interpreters (strictness and update -analysers). You can turn these off individually with --fno-strictness anti-option and -.-fno-update-analysis anti-option +The part of the compiler that is occasionally prone to wandering off +for a long time is the strictness analyser. You can turn this off +individually with . +-fno-strictness anti-option @@ -550,16 +549,19 @@ Use strip on your executables. -“I think I have a space leak…” Re-run your program with -,-Sstderr RTS option and remove all doubt! -(You'll see the heap usage get bigger and bigger…) [Hmmm…this -might be even easier with the -F2s RTS option RTS -option; so… ./a.out +RTS -Sstderr -F2s...] +“I think I have a space leak…” Re-run your program +with , and remove all doubt! (You'll +see the heap usage get bigger and bigger…) +[Hmmm…this might be even easier with the + RTS option; so… ./a.out +RTS +-Sstderr -G1...] +-G RTS option +-Sstderr RTS option -Once again, the profiling facilities () are the basic tool for demystifying the space -behaviour of your program. +Once again, the profiling facilities () are +the basic tool for demystifying the space behaviour of your program. -- 1.7.10.4