Bug 5429

Summary: --enable-debug should be useful
Product: xorg Reporter: Daniel Stone <daniel>
Component: Server/GeneralAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED INVALID QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: high CC: freedesktop, mmokrejs, peter.hutterer
Version: gitKeywords: janitor
Hardware: x86 (IA32)   
OS: Linux (All)   
i915 platform: i915 features:

Description Daniel Stone 2005-12-27 12:33:49 UTC
passing --enable-debug should actually be useful.  there are numerous #ifdefs
throughout the server to enable a whole ton of stuff -- the most common is DEBUG
and NDEBUG, plus all the EXA fallback debugging.  for the drivers, there's stuff
like RADEON_DEBUG too.

it would be nice if the defines were all DEBUG or XORG_DEBUG or something, so
--enable-debug could just add -DDEBUG to cflags.
Comment 1 Daniel Stone 2007-02-27 01:29:34 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 2 Ben Byer 2009-10-02 00:18:39 UTC
Is this really just asking for someone to search and replace all #ifdef FOO_DEBUG with #ifdef DEBUG, or is there something more nuanced here?
Comment 3 Peter Hutterer 2009-10-05 22:12:10 UTC
the reason why all these debugs exist is AFAICT that most developers only want them for a specific subsystem. Once you enable everything, there's a lot of noise in the log file.

Something more nuanced would be nice. A simple solution could still be that DEBUG enables whatever local debug there is. This allows developers to manually enable bits without having the whole spew.
Or we standardise the debug output that it's easier to grep on the prefix.
Comment 4 Adam Jackson 2018-06-12 18:44:34 UTC
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.