Logging and Debugging

• Student: ShubhamSinghal
• Mentors: HarlanStenn
• GSoC: GSoC Project Page

Summary

Related Items: GSoC2012LoggingDebugging, GSoC2010LoggingAndDebugging, GSoC2009LogDebug, GSoC2009LoggingAndDebugging, Bug #1093, Bug #1408, Bug #2028, Bug #2160, Bug #2227

Tasks

• Framework Design
• Documentation

Timeline

Date	Task	Description	% Done
09-27	Final Evaluation	Final Evaluations Deadline
10-01	Final Results	Final Results Announced
07-29	BO Midterm Evals	Mentors and students can begin submitting mid-term evaluations.
09-23	Firm "Pencils Down"	Mentors, students and organization administrators can begin submitting final evaluations to Google.
08-02	EO Midterm Evals	Mid-term evaluations deadline.
06-17	Coding Begins	Students begin coding for their GSoC projects
09-27	Code Samples	Students begin uploading code samples
05-27	Community Bonding	Students get to know mentors, read documentation, get up to speed to begin working on their projects.
09-16	Wrap-up	Suggested "Pencils Down" date. Take a week to scrub code, write tests, improve documentation, etc.

Discussion and Comments

Shubham, please note that some of the msyslog() items have (or had, depending on when I check something in) newlines at the end of the strings: "...\n" - the trailing \n is not wanted for syslog entries. But this means we will probably never want \n at the end of these strings as we can then add one if we are outputting to a TTY or FILE sink. It also means that if the current code has one directive for TTY or FILE output and the same directive for syslog, we should be able to replace this with a single call that says "output to both syslog and TTY/FILE ". There are also some cases (like libntp/audio.c) where we have plain printf() calls - these should be fixed, too.

-- HarlanStenn - 2013-06-27