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.
Thanks Herminio On Tue, Feb 2, 2016 at 4:08 PM, Herminio Hernandez, Jr. < [email protected]> wrote: > Mike, > > When I trace in gdb and let the program run I get the standard error: > > Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". > libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r300_dri.so > libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r300_dri.so > libGL error: No matching fbConfigs or visuals found > libGL error: failed to load driver: r300 > libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so > libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so > libGL error: No matching fbConfigs or visuals found > libGL error: failed to load driver: swrast > > 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. > > Herminio > > > > > On Jan 26, 2016, at 7:49 PM, Michel Dänzer <[email protected]> wrote: > > > > On 26.01.2016 19:15, Herminio Hernandez Jr. wrote: > >> Would the same thing apply swrast driver? I see glxgears trying to > >> fall back to it and relieving the same error. > > > > Possibly, though that's a bit weird indeed. Anyway, trace the code > > execution (e.g. in gdb) and see. > > > > > > -- > > Earthling Michel Dänzer | http://www.amd.com > > Libre software enthusiast | Mesa and X developer > > >
_______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
