Mysteries Of The Unknown!!!!
I am currently traveling to Memphis on business, but I am trying to figure out a couple difficult mysteries of the debugging world. I know someone out there can help!
1) What happened to the ‘Stack Trace Depth’ setting in GFlags? Why was it removed? Is the functionality just gone? I have a memory leak plaguing our customers, but our application is very complex and the level at which the allocation happens is much much much more than 16 levels. All the documentation I can find says to ‘change the Stack Trace depth edit control’ in gflags, but it doesn’t seem to be there!!!
2) How can I set a windbg breakpoint that breaks only when a certain path hasn’t been taken through the code to reach this point. In other words, if module!object::functionX is in the call stack, I do NOT want to break, but rather continue, until I reach this point from a different path. Do I have to do a ‘k’ combined with a .foreach command, and parse each stack? That will slow things down, but may work if I can get the syntax correct.
If I figure these out, I will post what I find…..or maybe someone out there can post something in the comments.