how to use ghci-debugger with packages

[Frederik Eaton]

On Mon, Feb 25, 2008 at 11:14:08AM +0000, Simon Marlow wrote:
> Frederik Eaton wrote:
> 
> >Thanks, I may try that. I'm currently trying to get my GNU-make-based
> >build to install profiling versions of package modules, in the hope
> >that -xc might give more useful information than it did a year ago...
> 
> I would think the chances of that are fairly low, there haven't been any significant 
> changes to the way cost centres work.

OK thanks... Actually I got the GHCi debugger to help me (having
discovered -fbreak-on-exception).

Frederik

P.S. Here are some suggestions for the GHCi debugger documentation:

http://www.haskell.org/ghc/dist/current/docs/users_guide/ghci-debugger.html

"There is one major restriction: breakpoints and single-stepping are only available in interpreted modules; compiled code is invisible to the debugger."
-->
"There is one major restriction: breakpoints and single-stepping are only available in interpreted modules; compiled code is invisible to the debugger. Note that packages only contain compiled code - so debugging a package requires finding its source and loading that directly."

"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."
-->
"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. For instance, it is possible to break automatically when an exception is thrown, even if it is thrown from within compiled code (see 3.5.6. Debugging exceptions)."