Changes between Version 96 and Version 97 of ExplicitCallStack


Ignore:
Timestamp:
Nov 16, 2017 9:50:52 PM (2 years ago)
Author:
bgamari
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ExplicitCallStack

    v96 v97  
    1414 then any crash (call to `error`) will yield an informative backtrace.  The backtrace gives you a stack of calls that looks very like what you'd get in a call-by-value language.  (Lots of papers about profiling in a lazy language, dating right back to [http://research.microsoft.com/~simonpj/papers/1997_profiling_TOPLAS.ps.gz Formally based profiling for higher order functional languages] give the background.)
    1515
    16  You need to compile your whole program with profiling, and you need a profiled version of the packages you install. You can do the latter by adding `--enable-pofiling` to Cabal, and you can put that in your `~/.cabal` file.
     16 You need to compile your whole program with profiling, and you need a profiled version of the packages you install. You can do the latter by adding `--enable-profiling` to Cabal, and you can put that in your `~/.cabal` file.
    1717
    1818 Programs run slower, of course, but that may not matter when debugging.  But a crash in a production system will generate no useful information.