Setting conditional breakpoints using object ids- January 17, 2007 In native code, its sometimes useful to set a breakpoint condition so that a breakpoint will only stop for a particular instance of an object. To do this, I simply use the address of the object: this == (CMyObject)0x10fc10 In managed code, the garbage collector moves objects around, so even if you were writing in a language that had great support for pointers, setting a conditional breakpoint this way is probably useless. Instead, you can do this using object ids. Step 1: Make an Object...http://blogs.msdn.com/greggm/archive/2007/01/17/setting-conditional-breakpoints-using-obje... Tracking down native leaks- January 17, 2007 I have been spending some time looking at native memory leaks recently, and I decided to blog about some of the techniques which worked well for me. First, find out what objects are leaking. If your code doesnt already have some sort of leak detection scheme, you can take advantage of the fact that the operating systems heap does. KB 268343 explains how to use UMDH to get a text file of all the leaking callstacks. Keep in mind that to get useful output, _NT_SYMBOL_PATH must point...http://blogs.msdn.com/greggm/archive/2007/01/16/tracking-down-native-leaks.aspx |