RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://docs.haskellstack.org/en/stable/topics/debugging/ below:

Debugging - Stack

Debugging¶

To profile a component of the current project, pass the --profile flag to stack build.

The flag:

for project packages, turns on the Cabal flag --enable-profiling;
turns on the Cabal flag --enable-library-profiling; and
passes GHC's +RTS -p runtime options to any test suites and benchmarks.

For example the following command will build the my-tests testsuite with profiling options and create a my-tests.prof file in the current directory as a result of the test run.

stack test --profile my-tests

The my-tests.prof file now contains time and allocation info for the test run.

To create a profiling report for an executable, e.g. my-exe, you can command:

stack exec --profile -- my-exe +RTS -p

For more fine-grained control of compilation options there are the --library-profiling flag and --executable-profiling flag.

The --library-profiling flag:

turns on the Cabal flag --enable-library-profiling; and
passes GHC's +RTS -p runtime options to any test suites and benchmarks.

The --executable-profiling flag:

for project packages, turns on the Cabal flag --enable-profiling;
turns on the Cabal flag --enable-library-profiling; and
passes GHC's +RTS -p runtime options to any test suites and benchmarks.

To enable compilation with profiling options by default you can add the following to a project-level or global configuration file:

build:
  library-profiling: true
  executable-profiling: true