From b2bb677672adb478425787563a9f344b70987105 Mon Sep 17 00:00:00 2001 From: Pepe Iborra Date: Thu, 26 Apr 2007 10:18:53 +0000 Subject: [PATCH] We don't have -fdebugging anymore, and fine tuning is not really necessary now --- docs/users_guide/ghci.xml | 19 ------------------- 1 file changed, 19 deletions(-) diff --git a/docs/users_guide/ghci.xml b/docs/users_guide/ghci.xml index 54ce6b7..9775c34 100644 --- a/docs/users_guide/ghci.xml +++ b/docs/users_guide/ghci.xml @@ -966,10 +966,6 @@ $ ghci -lm Permits to add, delete or list the breakpoints in a debugging session. - In order to make this command available, the - -fdebugging flag must be active. The easiest way is to launch - GHCi with the -fdebugging option. For more - details on how the debugger works, see . @@ -1606,9 +1602,6 @@ Prelude> :set -fno-glasgow-exts The module must have been loaded interpreted, i.e. not loaded from an .o file compiled by ghc - - The module must have been loaded with the -fdebugging flag - Using the debugger The debugger allows the insertion of breakpoints at specific locations in the source code. These locations are governed by event sites, and not by line as in traditional debuggers such as gdb. @@ -1918,11 +1911,6 @@ Just 20 Tips - * Use PRAGMAs to fine tune which modules are loaded under debugging mode - - {-# OPTIONS_GHC -fdebugging #-} - - * Repeated use of seq and :print may be necessary to observe unevaluated untyped bindings @@ -1962,13 +1950,6 @@ Main.hs:15> x' at the scope of a breakpoint if there is a explicit type signature. - - - Modules compiled by GHCi under the -fdebugging - flag will perform slower: the debugging mode introduces some overhead. - Modules compiled to object code by ghc are not affected. - - -- 1.7.10.4