<p>Agreed to all of the above. Libraries, even debug builds, should stay silent by default. We can (and should!) just doc the various env vars instead, IMHO.</p>
<p>Sending from a mobile, pardon the brevity. ~ C.</p>
<p>On Aug 5, 2010 6:20 PM, "Dave Airlie" <<a href="mailto:airlied@gmail.com">airlied@gmail.com</a>> wrote:<br type="attribution">> On Fri, Aug 6, 2010 at 11:17 AM, Jakob Bornecrantz <<a href="mailto:wallbraker@gmail.com">wallbraker@gmail.com</a>> wrote:<br>
>> This commit silences the printing off most of the debug information<br>>> when running debug builds. The big culprits are the the tgsi sanity<br>>> checker that gets run on all shaders on debug. All the options. And<br>
>> finaly the cpu caps printer.<br>>><br>>> This came after a discussion on #dri-devel that --enable-debug should<br>>> just make it possible to use gdb and not print a ton of stuff to stderr.<br>>><br>
>> My only hesitation is turning of the debug options since its rather<br>>> usefull to know which options you can play with.<br>>><br>>> Comments, acks and nacks please.<br>> <br>> ACK.<br>> <br>
> I'm all for this, I think mesa also does some output which really, not<br>> something we should be seeing unless we ask for it.<br>> <br>> Dave.<br>> _______________________________________________<br>
> mesa-dev mailing list<br>> <a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a><br>> <a href="http://lists.freedesktop.org/mailman/listinfo/mesa-dev">http://lists.freedesktop.org/mailman/listinfo/mesa-dev</a><br>
</p>