Summary: | Inconsistent use of both stderr and stdout for debug output | ||
---|---|---|---|
Product: | Mesa | Reporter: | Alexander Monakov <amonakov> |
Component: | Other | Assignee: | mesa-dev |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Alexander Monakov
2013-06-06 18:59:24 UTC
It seems like most of the messages should use one of _mesa_problem, _mesa_error, or _mesa_warning. We may even want an additional _mesa_info. The advantage of using these (instead of printf directly) is they also route through ARB_debug_output. printf and fprintf appear ~1500 times in the code base. Going through and changing all of them (and reviewing all the patches that result), doesn't seem like a good use of anyone's time. :( |
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.