Purify will instrument your object code and libraries by adding checking instructions before every memory operation. There is no need to recompile. Currently building in bldrecoq seems to be working, which makes using Purify quite a bit easier. Make sure that you place your cache directory somewhere which will be visible to any of the build machines. If you are running interactively, a browser window will appear when you start the program.
Error reports appear in the browser as they are detected during program execution.
The browser will remain active after the program terminates, until you close it yourself. You may also save the error reports to a file, and use the browser to study them at a later time. The browser is pretty straightforward to use. For each error detected it prints a summary line, telling you what type the error was and how many times it occurred. You can select a message and expand it so that it shows the sequence of calls leading to the error, the relevant lines of source code for each function in the calling sequence, and even pull up the source file in an editor window.