Frequently Asked Questions
Why do you call Hat a tracer rather than a debugger?
The word debugger suggests: firstly that there is a fault to be found; and secondly, that the tool will fix it. In actual fact, the tracer is just a tool for observing what happened in any particular program run. You can use it to find the cause of a fault, but equally, you can use it simply to aid your understanding of a correct program. While the tracer will help you to find bugs, it cannot find them for you. And once the bug is found, you must fix it, the tracer cannot!
Why did you not implement a conventional tracer/debugger as they are well known for imperative languages?
Conventional tracers (debuggers) for imperative languages allow the user to step through the program computation, stop at given points and examine variable contents. In our opinion this tracing method is unsuitable for a lazy functional language such as Haskell, because its evaluation order is complex, function arguments are usually unwieldy large unevaluated expressions, and generally computation details do not match the user's high-level view of functions mapping values to values. Also the stack used by the Haskell runtime system does not resemble the stack of function calls used by runtime systems of strict languages.
However, the trace file written by the traced program contains all information in the order of lazy evaluation. It is possible to write a viewing tool that admits single stepping through a lazy computation.
How much does tracing cost me in time and space?
Currently a traced program runs between 50-200 times slower than its untraced counterpart, depending which compiler and options you use. We are working on reducing this factor. As a rule of thumb, a reduction step produces about 50 bytes in the trace file. So trace files can easily grow to tens and hundreds of megabytes. However, you can name some modules of your program as trusted, so that their reductions are not recorded in the trace.
I have trouble compiling my program for tracing.
Hat covers the complete Haskell 98 language and its libraries, or at least that is the intention. It only supports a very few language extensions, such as the FFI. First make sure that your program is fully Haskell'98, and if it still won't compile, report it as a bug in Hat. [ Check the Hat Feature Summary to see exactly which parts of the language are missing, and when you can expect them to be added. ]
The latest updates to these pages are available on the WWW from http://www.cs.york.ac.uk/fp/hat/
This page last modified: 11 June 2002