<p>So my company uses a delightfully buggy program called Rational Purify (as a plugin to Microsoft Visual Developer Studio) to manage memory leaks.  The program is deigned to let you click on a memory leak after you have encountered it, and then jump to the line that the leak occurs on.</p>

<p>Unfortunately Purify is malfunctioning and Purify will not jump to the place that the leak occurred it only mentions the class and method that the leak occurs in.  Unfortunately, sometimes this is about as useful as hiring a guide to help you hunt bears and having him point to the forest and tell you there are bears there.</p>

<p>Does anyone with Purify experience have any idea how I might fix this problem or have a good manual to look though?</p>

[{'answer_id': 5952, 'author': 'Michal Sznajder', 'author_id': 501, 'author_profile': 'https://Stackoverflow.com/users/501', 'pm_score': 2, 'selected': False, 'text': '<p>Are you sure you have debug build? Or rather you have all PDB\'s enabled? Try WindDbg on your executable and check with !lmi command what is visible.</p>\n\n<p>Is whole code properly instrumented?</p>\n\n<p>Also consider using something else like <a href="http://www.codeproject.com/KB/applications/visualleakdetector.aspx" rel="nofollow noreferrer">free Visual Leak Detector</a> or Microsoft\'s tool LeakDiag.</p>\n'}, {'answer_id': 49944, 'author': 'Andy Brice', 'author_id': 455552, 'author_profile': 'https://Stackoverflow.com/users/455552', 'pm_score': 2, 'selected': False, 'text': "<p>I used Purify about 5 years ago. It was really flaky then. They kept promising to fix all the bugs in the 'next release'. We gave up on it in the end. One can only wonder if they used their own QA tools on their products. Oh the irony...</p>\n"}, {'answer_id': 81892, 'author': 'titanae', 'author_id': 2387, 'author_profile': 'https://Stackoverflow.com/users/2387', 'pm_score': 3, 'selected': True, 'text': "<p>Generally you have two options, one exclude modules DLL's from instrumentation in Purify, it helps some times. Second is get BoundsChecker, this does compile time instrumentation much slower but the level of detail is an order of magnitude better.</p>\n\n<p>We generally use Purify on check-in, sanity checking, and BoundsChecker when we know a bug/crash exists.</p>\n\n<p>BoundsChecker has some nice features like only instrument files A.cpp &amp; B.cpp, excluding all the rest.</p>\n\n<p>Be aware neither of these two applications function on 64 bit operating systems, and BoundsChecker will not install on 64 bit OS. Most frustrating if you make the switch to native 64 bit development with 32 bit back port!</p>\n"}, {'answer_id': 226654, 'author': 'Community', 'author_id': -1, 'author_profile': 'https://Stackoverflow.com/users/-1', 'pm_score': 2, 'selected': False, 'text': "<p>Purify is like a swiss knife. If you know how to use it, you will get some results, not the best but still results. If you don't, it will crash, because it is just another program running on Windows.</p>\n\n<p>In the end you will need a lot of patience, rebuilds and a bit of luck.</p>\n"}, {'answer_id': 714325, 'author': 'RichieHindle', 'author_id': 21886, 'author_profile': 'https://Stackoverflow.com/users/21886', 'pm_score': 2, 'selected': False, 'text': "<p>Purify comes with a script called ScanVSSolutionForPurifyPlus.pl which will ensure that your project files have all the right settings for Purify to work properly.  If you haven't run it, give it a go.</p>\n\n<p>(I've personally used ScanVSSolutionForPurifyPlus.pl on a large solution, and it worked like a charm.  One caveat: when you give it the name of your <code>.sln</code> file, you might need to give it the full pathname.)</p>\n"}]
['https://Stackoverflow.com/questions/5509', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/159/']