Bug 1310 – Default debug mode in nightly builds

Bug 1310 - Default debug mode in nightly builds

Summary:

Default debug mode in nightly builds

Status:	CLOSED WORKSFORME

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Misc
Version:	6.0.0
Platform:	PC All

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Blackketter Dean

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-04-04 20:32 UTC by Jack Coates
Modified:	2008-08-18 10:54 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jack Coates 2005-04-04 20:32:08 UTC

Debugging output should be automatically activated in the nightly builds. While
end-users can currently turn on debugging on request, this situation prevents
the unpredictable, intermittent and infrequent bugs from being properly
diagnosed. KDF points out that some debugging options produce voluminous output
and should be left out of a "default, always-on" nightly build profile.

Thoughts?

Comment 1 Blackketter Dean 2005-04-20 15:53:40 UTC

We should continue (and probably add) debugging information for detected issues (a la assert()), but 
choosing a set of debug flags for nightly builds is probably going to create more problems than it fixes.

Comment 2 Chris Owens 2008-03-11 11:28:07 UTC

This bug was marked resolved in Slimserver 6.1, which is several versions ago.  If you're still seeing this bug, please re-open it.  Thanks!