You probably need to ask Purify tech support.
Generally speaking, Purify makes deep assumptions about code generation details, and those details are not stable. The details can change in a compiler patch. It's possible that an unexpected code sequence caused the Purify instrumentation to fail.
The same problem I observed when the compiler is
CC: Sun C++ 5.8 2005/10/13
and purify
Version 2003a.06.15 FixPack 0214.
Without purify the program is running fine or with purify and optimization level <=O3.
(thread on IBM's rational forum, seems to be related)
http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?message=13865926& ;cat=24&thread=134524&treeDisplayType=threadmode1&forum=344#13865926
Does the Purify version number 003a.06.15 mean it is from 2003? If so, it is much older than the compiler. As I said originally, Purify depends on details of code generation that change from time to time. You cannot necessarily expect an old version of Purity to work with a new compiler.
Check with Purity tech support.