[Mesa-dev] gdb doesnt step into GL API calls of gears.
kumar210in at gmail.com
Wed Apr 13 07:49:11 PDT 2011
OK. i tried your command i.e. "./configure --enable-debug
and did "make".
I also ran "scons libgl-xlib" which i guess wasnt necessary. Correct me
if i am wrong?
Now i set the LD_LIBRARY_PATH to lib/gallium and run gears. i see around
60fps on my AMD athlon x2. I tried gdb with gears and now it allows me
to step into the gl calls also.
Now would like to understand a few things that i did above:
a. is the libGL.so built (using the above commands i.e. configure and
make) under mesa/lib/gallium completely self-sufficient? Doesnt it need
swrast_dri.so or swrastg_dri.do?
b. On your comment "I don't recall if we ever made softpipe work as a
DRI driver.". Whats the purpose of swrastg_dri.so then? where and when
is this lib used?
Btw Thanks Brian for your replies. This is my spare time project; hence
the delay in response.
On Tue, 2011-04-12 at 08:14 -0600, Brian Paul wrote:
> On 04/11/2011 11:52 PM, kumar vemuri wrote:
> > Hi Brian,
> > I did use --enable-debug with configure. But still i dont see gdb
> > stepping into gl calls... it does step into the glu calls though.
> > This is my configure command: ./configure --enable-debug
> > --enable-gallium-i915 --enable-gallium-swrast --with-dri-drivers=swrast
> Try this:
> ./configure --enable-debug --enable-gallium-swrast --with-driver=xlib
> > By the way, dont know if its of any importance but ..
> > I have an nvidia blob running on my pc. So to get the gallium softpipe
> > setup working i am using the libGL.so generated by "scons libgl-xlib"
> > under build/linux-<platform>/lib. And i set the LIBGL_DRIVERS_PATH to
> > lib/gallium so that the libGL picks up the swrastg_dri.so but i dont
> > have the swrast_dri.so under lib/gallium.
> > Also, another question: Do i have to link the swrast_dri.so to
> > swrastg_dri.so in lib/gallium for softpipe setup to work?
> I don't recall if we ever made softpipe work as a DRI driver.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mesa-dev