On 25.01.2016 10:56, Herminio Hernandez, Jr. wrote: > So I believe I have all the debugging symbols installed. From what I > am seeing in gdb and valgrind I am still thinking the issue is in the > glx branch. For gdb I ran it twice and stopped it during it attempt > to load the r300 driver and in it attempt to load the swrast driver. > Both failed at the same place in the trace see below. Some is > breaking when dlopen tries to load the driver. Just want to verify > that I am looking at the right thing.
I'm afraid not. The leaks are probably just due to failing to clean up some things in error paths. You need to work back from the point where dri2CreateScreen fails. Assuming it still prints "libGL error: No matching fbConfigs or visuals found" for you, it can only be one (or both) of the driConvertConfigs calls failing, probably because the r300 driver says it doesn't support the Gallium formats which the code in src/gallium/state_trackers/dri/ computes as corresponding to the DRI formats. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer
signature.asc
Description: OpenPGP digital signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev