I guess if all it was is a kind of history buffer, that was loaded and flushed as scripting went, it wouldnt be overly cpu intensive to add.
Might i suggest that it can be switched ON and OFF, since the script i/you might write to display its contents , itself must execute commands, and would thus start destroying the tracing data
