Hi James, 1) Try: GALLIUM_TRACE=~/gallium.trace ./gbmtest
2) Trace is an optional component, so make sure it's built in your driver. See for example src/gallium/targets/dri-r600/Makefile.am to know how to add it. 3) The easiest way to debug gallium is to use a debugger. Marek On Wed, Sep 18, 2013 at 2:08 AM, James Simmons <[email protected]> wrote: > > Hello. > > I'm the main developer from the Openchrome project and we have > reached the point were work is being started for the Gallium driver for > VIA hardware. To help develope a stable simple start I decided to go for > bare bones libgbm support using a gallium backend. So like any start my > simple libgbm app fails at the start. Well to figure it out I need to > debug my gallium driver. So I started to read up on how to debug gallium > and so I attempted to use the trace pipe driver. So the command I used > was > > GALLIUM_TRACE=~/gallium.trace;./gbmtest > > but no XML file was generated. What am I doing wrong? How do I properly > debug? Thanks for your help. Once I get this working I will push to > master. > _______________________________________________ > mesa-dev mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/mesa-dev _______________________________________________ mesa-dev mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/mesa-dev
