Summary:	ASTERISK-05950: debug output prefixes too much with date/time/file
Reporter:	Andrew Kohlsmith (akohlsmith)	Labels:
Date Opened:	2006-01-02 09:35:09.000-0600	Date Closed:	2006-01-12 08:27:10.000-0600
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	"pri debug span" in particular: what it should spit out: Jan  2 11:28:31 DEBUG[6762] chan_zap.c: > [ 18 03 a9 83 81 ] What it *does* spit out: Jan  2 11:28:31 DEBUG[6762] chan_zap.c: > [Jan  2 11:28:31 DEBUG[6762] chan_zap.c: 18Jan  2 11:28:31 DEBUG[6762] chan_zap.c:  03Jan  2 11:28:31 DEBUG[6762] chan_zap.c:  a9Jan  2 11:28:31 DEBUG[6762] chan_zap.c:  83Jan  2 11:28:31 DEBUG[6762] chan_zap.c:  81Jan  2 11:28:31 DEBUG[6762] chan_zap.c: ] ****** ADDITIONAL INFORMATION ****** It appears that at some point the logger function changed from simply spitting out what it was given to spitting out the entire line header + what was given, but the debug functions weren't updated to use an alternate function that did what the original logger function did. This makes it unbelievably difficult to try and work out what's going on without postprocessing the debug output in a text editor.
Comments:	By: Tilghman Lesher (tilghman) 2006-01-02 10:08:38.000-0600 Or someone simply forgot to add a newline in their debug statement. By: Andrew Kohlsmith (akohlsmith) 2006-01-02 10:09:37.000-0600 Uh, no.  Read the bug report again.  Adding a newline will not give the intended (original) output. By: Matthew Fredrickson (mattf) 2006-01-04 08:07:54.000-0600 I just put in the fix in bug 6125, check to see if this makes the output more readable.