Add logging
By adding logging using some library we can write the log file to disk; portions of this can be included in error reports to help debug a crash.
Logging can help during development to see what's going on behind the scenes without having to stick "print"s everywhere.
Blueprint information
- Status:
- Complete
- Approver:
- Steven Sproat
- Priority:
- Medium
- Drafter:
- Steven Sproat
- Direction:
- Approved
- Assignee:
- Steven Sproat
- Definition:
- Approved
- Series goal:
- Accepted for 1.0
- Implementation:
- Implemented
- Milestone target:
- 1.0
- Started by
- Steven Sproat
- Completed by
- Steven Sproat
Whiteboard
INFO 2011-06-10 03:41:34,342 Program starting
[...]
INFO 2011-06-10 03:41:34,687 Startup complete, time taken: 0.344ms
INFO 2011-06-10 03:41:41,030 User loading file [C:\Documents and Settings\Steve\My Documents\
INFO 2011-06-10 03:41:41,030 Opening file [C:\Documents and Settings\Steve\My Documents\
DEBUG 2011-06-10 03:41:41,030 Attempting to load file [C:\Documents and Settings\Steve\My Documents\
INFO 2011-06-10 03:41:41,030 Attempting to convert [C:\Documents and Settings\Steve\My Documents\
DEBUG 2011-06-10 03:41:41,030 PDF is cached
DEBUG 2011-06-10 03:41:41,030 Opening new sheet [liuetal2003a.pd - 1]
DEBUG 2011-06-10 03:41:41,062 Loading [C:\Documents and Settings\
DEBUG 2011-06-10 03:41:41,108 Opening new sheet [liuetal2003a.pd - 2]
DEBUG 2011-06-10 03:41:41,140 Loading [C:\Documents and Settings\
....
DEBUG 2011-06-10 03:41:41,578 Opening new sheet [liuetal2003a.pd - 8]
DEBUG 2011-06-10 03:41:41,608 Loading [C:\Documents and Settings\
Program has 2 debug flags: one write to a file, other to stdout. Whyteboard also has another logger that keeps track of all logged messages and adds these to the email when reporting a bug