X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fghci.xml;h=b1e36ec8403f63bcddf218e3368537ea028e3ba6;hb=1a38a09d1077b507a0a4e1ebba8e1b51bd5fede9;hp=a8ebbd7b661b9f21d9d8713a2cbd2dc3284b1cdd;hpb=f17c76a4fc51a52ccda154ec9e4990f13f78c8c2;p=ghc-hetmet.git

diff --git a/docs/users_guide/ghci.xml b/docs/users_guide/ghci.xml
index a8ebbd7..b1e36ec 100644
--- a/docs/users_guide/ghci.xml
+++ b/docs/users_guide/ghci.xml
@@ -1109,8 +1109,10 @@ right :: [a]
         bug. GHCi offers two variants of stepping. Use 
 	<literal>:step</literal>  to enable all the
         breakpoints in the program, and execute until the next breakpoint is
-        reached. Use <literal>:stepover</literal> to step over function
-	applications, which of course are executed all the same. 
+        reached. Use <literal>:steplocal</literal> to limit the set
+	of enabled breakpoints to those in the current top level function.
+	Similarly, use <literal>:stepmodule</literal> to single step only on
+	breakpoints contained in the current module.
 	For example:</para>
 
 <screen>
@@ -1333,9 +1335,13 @@ a :: a
         <literal>:trace</literal> and <literal>:history</literal> to establish
         the context.  However, <literal>head</literal> is in a library and
         we can't set a breakpoint on it directly.  For this reason, GHCi
-        provides the flag <literal>-fbreak-on-exception</literal> which causes
-        the evaluator to stop when an exception is thrown, just as it does when
-        a breakpoint is hit.  This is only really useful in conjunction with
+        provides the flags <literal>-fbreak-on-exception</literal> which causes
+        the evaluator to stop when an exception is thrown, and <literal>
+	-fbreak-on-error</literal>, which works similarly but stops only on 
+	uncaught exceptions. When stopping at an exception, GHCi will act 
+	just as it does when a breakpoint is hit, with the deviation that it
+	will not show you any source code location. Due to this, these 
+	commands are only really useful in conjunction with
         <literal>:trace</literal>, in order to log the steps leading up to the
         exception.  For example:</para>