Devel::AutoTrace - Currently a half baked idea on how to do automatic loging of a codebase such that you can know where the cruft is.
> perl -d:AutoTrace my_script.pl
> cat /tmp/devel_autotrace.log
[43a3a8bf38dfabe838eeac5a9daa2180:1309665646.17477] my_host : ./my_script.pl : start
[43a3a8bf38dfabe838eeac5a9daa2180:1309665647.40194] my_host : ./my_script.pl : end
> cat /tmp/43a3a8bf38dfabe838eeac5a9daa2180.traceuse
... {{EXPLAIN WHATS GOING ON HERE}}
Currently this is done via %ENV, this might change
Default is to write to '/tmp', setting $ENV{AUTOTRACE_LOGROOT} will override this. You are require to make sure that path exists.
Default is 'devel_autotrace.log', set $ENV{AUTOTRACE_LOGFILE} to change.
Default is to build a md5_hex from hostname, $0, time, and a random number.
Current log format is: [AUTOTRACE_UID:time_hires] hostname : $0 : $msg\n
Currently only 'start' and 'end' are tracked.
Devel::TraceUse is used to build a stack trace that is saved to AUTOTRACE_LOGROOT/AUTOTRACE_UID.traceuse.
Only 'start' and 'end' are tracked.
ATLOG is not exported... should it be?
Devel::TraceUse is called from Devel::AutoTrace context thus the heading on the report is wrong.