<p>I have a crash dump of an application that is supposedly leaking GDI.  The app is running on XP and I have no problems loading it into WinDbg to look at it.  Previously we have use the <a href="http://msdn.microsoft.com/en-us/library/cc267206.aspx" rel="noreferrer">Gdikdx.dll extension</a> to look at Gdi information but this extension is not supported on XP or Vista. </p>

<p>Does anyone have any pointers for finding GDI object usage in WinDbg.  </p>

<p>Alternatively, I do have access to the failing program (and its stress testing suite) so I can reproduce on a running system if you know of any 'live' debugging tools for XP and Vista (or Windows 2000 though this is not our target).</p>

There was a
MSDN Magazine article from several years ago
that talked about GDI leaks.  This points to several different places with good information.
In WinDbg, you may also try the
```
!poolused
```
command for some information.
Finding resource leaks in from a crash dump (post-mortem) can be difficult -- if it was always the same place, using the same variable that leaks the memory, and you're lucky, you could see the last place that it will be leaked, etc.  It would probably be much easier with a live program running under the debugger.
You can also try using
Microsoft Detours
, but the license doesn't always work out.  It's also a bit more invasive and advanced.