[Remove text about ghcprof. It almost certainly doesn't work. Simon Marlow **20070829122126] { hunk ./docs/users_guide/profiling.xml 243 - flattened into a tree. The XML profiling tool (described in ) will be able to display real loops in - the call-graph. + flattened into a tree. hunk ./docs/users_guide/profiling.xml 454 - - - : - - - - The option generates profiling - information in the XML format understood by our new - profiling tool, see . - - - hunk ./docs/users_guide/profiling.xml 948 - - - - Graphical time/allocation profile - - You can view the time and allocation profiling graph of your - program graphically, using ghcprof. This is a - new tool with GHC 4.08, and will eventually be the de-facto - standard way of viewing GHC profilesActually this - isn't true any more, we are working on a new tool for - displaying heap profiles using Gtk+HS, so - ghcprof may go away at some point in the future. - - - To run ghcprof, you need - uDraw(Graph) installed, which can be - obtained from uDraw(Graph). Install one of - the binary - distributions, and set your - UDG_HOME environment variable to point to the - installation directory. - - ghcprof uses an XML-based profiling log - format, and you therefore need to run your program with a - different option: . The file generated is - still called <prog>.prof. To see the - profile, run ghcprof like this: - - - - -$ ghcprof <prog>.prof - - - which should pop up a window showing the call-graph of your - program in glorious detail. More information on using - ghcprof can be found at The - Cost-Centre Stack Profiling Tool for - GHC. - }