http://www.advancedwindowsdebugging.com/forums/forums/5/ShowForum.aspxGeneral discussion about the Advanced Windows Debugging book.enCommunityServer 2.1 (Build: 60809.935)http://www.advancedwindowsdebugging.com/forums/forums/thread/750.aspxWed, 16 Jul 2008 15:56:20 GMT8fe6c8b0-35bd-46d7-a742-2d438749dbe0:750jonw0http://www.advancedwindowsdebugging.com/forums/forums/thread/750.aspxhttp://www.advancedwindowsdebugging.com/forums/forums/commentrss.aspx?SectionID=5&PostID=750<p>&nbsp;</p><p>Hi,</p><p>I am experiencing a problem with call stacks in DebugDiag.&nbsp;&nbsp;I&#39;m tracing down some memory leaks and I found DebugDiag to be very useful, I&#39;m glad your book pointed this out. &nbsp;One thing I noticed is that the stack walk depth is not the entire stack frame.&nbsp; 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&nbsp;with a virtual function call.&nbsp; Most of the time there seem to be functions missing between the last displayed entry and the bottom of the stack.&nbsp; Have you seen or heard of any issue like this with DebugDiag?&nbsp; I am hoping to be able to see the entire call stack.&nbsp; Do you know of a way to fix this?</p><p>Also, just a curiosity, does DebugDiag have any relation to LeakDiag?</p><p>&nbsp;Thanks for your help and fantastic book!&nbsp; jonw<br /></p>