On Thu, Oct 18, 2001 at 08:47:40PM -0700, Mark Vojkovich wrote: > On Thu, 18 Oct 2001, Justin Husted wrote: > > > On Wed, Oct 17, 2001 at 07:44:02PM -0700, Mark Vojkovich wrote: > > > On Wed, 17 Oct 2001, Justin Husted wrote: > > > > > > > Hi, > > > > > > > > I've been looking for a useful way to debug client resource leaks with X > > > > without much luck, so I thought I'd ask here. > > > > > > In xc/programs/Xserver/dix/resource.c:FreeClientResources() the > > > resources that are left unfreed when the client quits/dies are cleaned > > > up. You can see their XIDs and types (ie. pixmap, colormap, etc...) > > > in that function. Maybe that is of use to you. > > > > Thanks... > > > > This seems to work fairly well, though of course the information given is > > somewhat limited. > > You can cast the "this->value" to the type (ie. PixmapPtr, WindowPtr, > GCPtr etc...) and see the data structures for those objects. In > case printing out the sizes, etc... would help figure out which > objects in particular that were getting leaked. You can't get that > kind of information on the client's end.
True, but a stack trace from the moment the resource was allocated would be even more useful, and you can get that on the client's end. :-) -J _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
