<div dir="ltr"><div><div>I have done some more debugging and I do have a question. The clearest, repeatable issue I am seeing is when I run glxgears in apitrace. The crash always occrs at GLXChooseVisual. It returns NULL and from the documentation this means that it is encountering an undefined attribute. I see this when I am running either Ubuntu or Debian. The other tools (ie gdb and valgrind) have not given as clear an indication where the problem is (granted I admit that I may be not using them correctly either). My question is how would I determine what is causing this? I have search and have not found a clear explanation on how to troubleshoot this on the web. <br><br></div>Thanks<br></div>Herminio<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 2, 2016 at 4:08 PM, Herminio Hernandez, Jr. <span dir="ltr"><<a href="mailto:herminio.hernandezjr@gmail.com" target="_blank">herminio.hernandezjr@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Mike,<br>
<br>
When I trace in gdb and let the program run I get the standard error:<br>
<span class=""><br>
Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".<br>
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r300_dri.so<br>
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r300_dri.so<br>
</span><span class="">libGL error: No matching fbConfigs or visuals found<br>
</span>libGL error: failed to load driver: r300<br>
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so<br>
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so<br>
<span class="">libGL error: No matching fbConfigs or visuals found<br>
</span>libGL error: failed to load driver: swrast<br>
<br>
Both r300 and swrast driver fail to load and I do not get a backtrace. When run gdb again and force an interrupt at the point the r300 fails to load I see in the trace that it is failing at the driOpenDriver function. When I run the program again and stop when the swrast driver fails in the trace I see it fail at the same spot. Unless I am reading the backtrace wrong I think that is where is the issue is. I am attaching the file so you can see.<br>
<span class="HOEnZb"><font color="#888888"><br>
Herminio<br>
<br>
</font></span><br><br>
> On Jan 26, 2016, at 7:49 PM, Michel Dänzer <<a href="mailto:michel@daenzer.net">michel@daenzer.net</a>> wrote:<br>
><br>
> On 26.01.2016 19:15, Herminio Hernandez Jr. wrote:<br>
>> Would the same thing apply swrast driver? I see glxgears trying to<br>
>> fall back to it and relieving the same error.<br>
><br>
> Possibly, though that's a bit weird indeed. Anyway, trace the code<br>
> execution (e.g. in gdb) and see.<br>
><br>
><br>
> --<br>
> Earthling Michel Dänzer | <a href="http://www.amd.com" rel="noreferrer" target="_blank">http://www.amd.com</a><br>
> Libre software enthusiast | Mesa and X developer<br>
<br>
<br></blockquote></div><br></div>