X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fghci.xml;h=35aa7cd279e4cf48400447b93c1425946f8f5c92;hb=9d03becc597e5b1ab6c8466209a1263bf8ba6f29;hp=5daa29c9a12eb6faf5d9c6db5834e449bd9c5baa;hpb=878ce92d0559e10a083b6983f2d23380086026d8;p=ghc-hetmet.git
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