From 987f467ca47d22a2453758c994c46c7da7bfc0d2 Mon Sep 17 00:00:00 2001 From: simonmar Date: Thu, 3 May 2001 09:34:40 +0000 Subject: [PATCH] [project @ 2001-05-03 09:34:40 by simonmar] document the +RTS -xc option --- ghc/docs/users_guide/runtime_control.sgml | 34 +++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 7 deletions(-) diff --git a/ghc/docs/users_guide/runtime_control.sgml b/ghc/docs/users_guide/runtime_control.sgml index f3b8eda..9dc6e14 100644 --- a/ghc/docs/users_guide/runtime_control.sgml +++ b/ghc/docs/users_guide/runtime_control.sgml @@ -304,6 +304,17 @@ + num + -DRTS option + + An RTS debugging flag; varying quantities of output + depending on which bits are set in + num. Only works if the RTS was + compiled with the option. + + + + file RTS option ticky ticky profiling @@ -327,14 +338,23 @@ - - num - -DRTS option + + + RTS + option - An RTS debugging flag; varying quantities of output - depending on which bits are set in - num. Only works if the RTS was - compiled with the option. + (Only available when the program is compiled for + profiling.) When an exception is raised in the program, + this option causes the current cost-centre-stack to be + dumped to stderr. + + This can be particularly useful for debugging: if your + program is complaining about a head [] + error and you haven't got a clue which bit of code is + causing it, compiling with -prof + -auto-all and running with +RTS -xc + -RTS will tell you exactly the call stack at the + point the error was raised. -- 1.7.10.4