Simple and effective--copy in the files, link the library and read off memory leaks in the exact same way you do compiler errors.
Not only that, it has a stack trace that Visual Studio recognizes (so actual lines of files are linked) and gives you a preview of the leaked memory. It deserves a post of its own in his blog because it's helped me on so many occasions, and did so once again today.
No comments:
Post a Comment