From dae4e17c803f604ed71dc4d2d93809e88884ffd8 Mon Sep 17 00:00:00 2001 From: sewardj Date: Tue, 20 Mar 2001 12:50:14 +0000 Subject: [PATCH] [project @ 2001-03-20 12:50:14 by sewardj] Document new profiling options. --- ghc/docs/users_guide/profiling.sgml | 69 +++++++++++++++++++++++++++++++++++ 1 file changed, 69 insertions(+) diff --git a/ghc/docs/users_guide/profiling.sgml b/ghc/docs/users_guide/profiling.sgml index 5929428..a29b160 100644 --- a/ghc/docs/users_guide/profiling.sgml +++ b/ghc/docs/users_guide/profiling.sgml @@ -594,6 +594,75 @@ $ ghcprof <prog>.prof + : + + heap profile filtering options + + It's often useful to select just some subset of the + heap when profiling. To do this, the following filters are + available. You may use multiple filters, in which case a + closure has to satisfy all filters to appear in the final + profile. Filtering criterion are independent of what it is + you ask to see. So, for example, you can specify a profile + by closure description (-hD) but ask to + filter closures by producer module (-hm{...}). + + + Available filters are: + + + + + : + + Restrict to one of the specified cost centers. + Since GHC deals in cost center stacks, the specified + cost centers pertain to the top stack element. For + example, -hc{Wurble,Burble} selects + all cost center stacks whose top element is + Wurble or + Burble. + + + + + + : + + Restrict to closures produced by functions in + one of the specified modules. + + + + + + : + + Restrict to closures whose description-string is + one of the specified descriptions. Description + strings are pretty arcane. An easy way to find + plausible strings to specify is to first do a + -hD profile and then inspect the + description-strings which appear in the resulting profile. + + + + + + : + + Restrict to closures having one of the specified + types. + + + + + + + + + : -- 1.7.10.4