[Intel-gfx] [PATCH 01/10] intel: shared header for shader debugging

Ben Widawsky ben at bwidawsk.net
Wed Jul 27 17:40:35 CEST 2011


On Wed, Jul 27, 2011 at 05:16:31PM +0200, Julien Cristau wrote:
> On Wed, Jul 27, 2011 at 15:08:08 +0000, Ben Widawsky wrote:
> 
> > On Thu, Jul 21, 2011 at 11:22:12PM +0200, Julien Cristau wrote:
> > > On Thu, Jul 21, 2011 at 13:54:41 +0000, Ben Widawsky wrote:
> > > 
> > > > On Tue, Jul 19, 2011 at 11:06:17PM +0200, Julien Cristau wrote:
> > > > > On Wed, Jul 13, 2011 at 13:51:43 -0700, Ben Widawsky wrote:
> > > > > 
> > > > > > +#define SHADER_DEBUG_SOCKET "/tmp/gen_debug"
> > > > > 
> > > > > Not sure what this is used for, but does it really need to be in /tmp?
> > > > 
> > > > It is the shared socket between a debug client (ie. Mesa) and the 
> > > > debugger. I don't care where it goes, do you have any recommendations?
> > > > 
> > > Somewhere under $HOME is probably better than a predictable file name in
> > > /tmp.
> > 
> > $HOME is not great because it requires a little hackery to accomplish.
> > The debugger will be running as root, and so if we put it in root's
> > $HOME, mesa may not be able to reach it.
> > 
> Ah, I didn't realise this would run as root.  Would /run (or /var/run)
> be ok then?  Alternately, use an abstract domain socket to not have to
> care about the underlying filesystem.

I wasn't even aware of abstract domain sockets. Seems like fun, let me try that
one first.

Ben



More information about the Intel-gfx mailing list