From e16acfd0329fbd10a1ff1bf808eb3b795fe1f56c Mon Sep 17 00:00:00 2001 From: Simon Marlow Date: Tue, 26 Feb 2008 10:26:12 +0000 Subject: [PATCH 1/1] documentation improvements from Frederik Eaton --- docs/users_guide/ghci.xml | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/docs/users_guide/ghci.xml b/docs/users_guide/ghci.xml index 5daa29c..35aa7cd 100644 --- a/docs/users_guide/ghci.xml +++ b/docs/users_guide/ghci.xml @@ -845,10 +845,12 @@ def = toEnum 0 GHCi contains a simple imperative-style debugger in which you can stop a running computation in order to examine the values of variables. The debugger is integrated into GHCi, and is turned on by - default: no flags are required to enable the debugging facilities. There - is one major restriction: breakpoints and single-stepping are only - available in interpreted modules; compiled code is - invisible to the debugger. + default: no flags are required to enable the debugging + facilities. There is one major restriction: breakpoints and + single-stepping are only available in interpreted modules; + compiled code is invisible to the debuggerNote that packages + only contain compiled code, so debugging a package requires + finding its source and loading that directly.. The debugger provides the following: @@ -883,9 +885,12 @@ def = toEnum 0 There is currently no support for obtaining a “stack - trace”, but the tracing and history features provide a useful - second-best, which will often be enough to establish the context of an - error. + trace”, but the tracing and history features provide a + useful second-best, which will often be enough to establish the + context of an error. For instance, it is possible to break + automatically when an exception is thrown, even if it is thrown + from within compiled code (see ). Breakpoints and inspecting variables -- 1.7.10.4