[m-rev.] for review: document trace count tools

[Ralph Becket]

Ian MacLarty, Wednesday, 13 September 2006:
> Estimated hours taken: 1.5
> Branches: main, 0.13
> 
> doc/user_guide.texi:
> 	Add a new section "Trace counts" to the debuggin chapter.
> 	Document the mtc, mslice, mdice and mtc_union tools.
> 
> mdbcomp/slice_and_dice.m:
> 	Fix a comment.
> 
> slice/mtc_union.m:
> 	Fix an incorrect usage message.
> 
> Index: doc/user_guide.texi
> ===================================================================
> RCS file: /home/mercury1/repository/mercury/doc/user_guide.texi,v
> retrieving revision 1.489
> diff -u -r1.489 user_guide.texi
> --- doc/user_guide.texi	4 Sep 2006 01:47:34 -0000	1.489
> +++ doc/user_guide.texi	13 Sep 2006 02:51:22 -0000
> @@ -1193,6 +1193,7 @@
>  * I/O tabling::
>  * Debugger commands::
>  * Declarative debugging::
> +* Trace counts::
>  @end menu
>  
>  @node Quick overview
> @@ -3706,10 +3707,10 @@
>  This can be done by compiling the program with deep tracing enabled
>  (either by compiling in a .debug or .decldebug grade
>  or with the @samp{--trace deep} or @samp{--trace rep} compiler options)
> -and then running the program
> -with the MERCURY_OPTIONS environment variable set to @samp{--trace-count}.  
> -This will generate a file called @samp{.mercury_trace_counts}
> -which contains a summary of the program's execution.
> +and then running the program under mtc.
> +This will generate a file with the prefix
> + at samp{.mercury_trace_counts} and a unique suffix,

Is this the right way around (prefix/suffix)?  The same appears in the
detailed description later.

-- Ralph
--------------------------------------------------------------------------
mercury-reviews mailing list
Post messages to:       mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au
--------------------------------------------------------------------------