Hi,

I am experiencing a problem with call stacks in DebugDiag.  I'm tracing down some memory leaks and I found DebugDiag to be very useful, I'm glad your book pointed this out.  One thing I noticed is that the stack walk depth is not the entire stack frame.  At first I thought this to be a hard coded limit as I found in the script files, but it seems that the call stack may terminate prematurely with a virtual function call.  Most of the time there seem to be functions missing between the last displayed entry and the bottom of the stack.  Have you seen or heard of any issue like this with DebugDiag?  I am hoping to be able to see the entire call stack.  Do you know of a way to fix this?

Also, just a curiosity, does DebugDiag have any relation to LeakDiag?

 Thanks for your help and fantastic book!  jonw