From 1a38a09d1077b507a0a4e1ebba8e1b51bd5fede9 Mon Sep 17 00:00:00 2001 From: Pepe Iborra Date: Tue, 11 Sep 2007 10:19:44 +0000 Subject: [PATCH] Documentation for -fbreak-on-error --- docs/users_guide/flags.xml | 12 ++++++++++++ docs/users_guide/ghci.xml | 10 +++++++--- 2 files changed, 19 insertions(+), 3 deletions(-) diff --git a/docs/users_guide/flags.xml b/docs/users_guide/flags.xml index 33c4e32..b417f7e 100644 --- a/docs/users_guide/flags.xml +++ b/docs/users_guide/flags.xml @@ -503,6 +503,18 @@ - + + Break on any exception thrown + dynamic + + + + + Break on uncaught exceptions and errors + dynamic + + + Turn off printing of binding results in GHCi dynamic diff --git a/docs/users_guide/ghci.xml b/docs/users_guide/ghci.xml index 69078d5..b1e36ec 100644 --- a/docs/users_guide/ghci.xml +++ b/docs/users_guide/ghci.xml @@ -1335,9 +1335,13 @@ a :: a :trace and :history to establish the context. However, head is in a library and we can't set a breakpoint on it directly. For this reason, GHCi - provides the flag -fbreak-on-exception 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 -fbreak-on-exception which causes + the evaluator to stop when an exception is thrown, and + -fbreak-on-error, 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 :trace, in order to log the steps leading up to the exception. For example: -- 1.7.10.4