Much as I find the debugger a nice tool to use, there comes a time when you
just want to get a little more error information than standard, but don't want
the hassle of setting up the debugger or of typing in loads of trace
instructions and print out comments (and yes - I do use the inspect function).
Hence my question: Does anyone have any code that can be `toggled on/off' to
show the following:
1 That a procedure has been called, what is passed into/received from it.
2 The value of lvars within a procedure as they change.
3 Which branches of control structures are taken, and why.
4 The user stack contents as they change.
5 Any other useful things anyone can think of....
Thanks,
Tim
--
---------------------------------------------------------------------
Tim Read, Email: tmr@cs.bham.ac.uk, The Attention and Affect Project,
Cognitive Science Research Centre, School of Computer Science,
The University of Birmingham, Edgbaston, Birmingham, B15 2TT, England
Phone: +44-(0)21-414-4766, Fax: +44-(0)21-414-4281
---------------------------------------------------------------------
|