[m-dev.] Question about the current Mercury trace

[Fergus Henderson]

On 27-Sep-2000, Zoltan Somogyi <zs at cs.mu.OZ.AU> wrote:
> 
> There are two issues here. I think there should be a trace level that
> is basically the current --trace deep plus these four events, while there
> is also a case for retaining the functionality of the current --trace deep.
> The question is which should be the default in debug grades.
> 
> The difference between --trace decl and the new grade would be that (a)
> --trace decl reserves two stack slots for the declarative debugger, and (b)
> it preserves the names of all variables, even those which are not live at
> any event. The former should not be necessary any more, and the latter
> difference could be erased by always keeping all variable names, since this
> has no time cost and only a reasonably small space cost.
> 
> I think we should consider making the trace level with all the possible event
> types (a version of --trace decl without the extra stack slots) the default,
> but only after experiments to determine the space and time overheads, as
> Fergus suggested. The simplest way to perform these experiments is to
> implement the option requested by Erwan in some form.
> 
> I think probably the best form is a single string option, called e.g.
> --suppress-events, which takes as its args a comma-separated list of
> event names or event class names to suppress. This could replace
> --no-trace-redo and --no-trace-internal, and I could implement it
> in a couple of hours.
> 
> Comments?

That all sounds good to me.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>  |  of excellence is a lethal habit"
PGP: finger fjh at 128.250.37.3        |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------