DevOps, CI/CD and Automation

heya,

I have a question that i REALLY REALLY REALLY REALLY hope somebody on this group can help me with;

Long story short I've been lumped with a massive codebase thats in production and it's my job to fine tune/refactor/clean up the bad boy. It's riddled with memory leaks (not mine but my predececessors) and I have to fix the;

Here's my problem.


Environment:

1) Forte C++ version 6
2) Solaris 8


The app in question uses the jni interface and therefore instantiates a JVM. The problem is that I cannot, cannot purify the app. As soon as the jvm gets instantiated, purify bombs out on me. The version of purify I'm using is the in-house latest (2003 beta something...). It is 2003 and it is a beta release of purify, I'm at home now, hence the ambiguity wrt forte and purify version details. I can provide them if needed.


Now my question is this;


1) Is this a known issue?
2) Is there a later version of purify that will successfully get past the point of jvm instantiation and allow me to rid this evil, dirty, bad application of all those nasty memory leaks.?



The reason I need to know 2) definitively is because I'm about to ask these people in this very very very very large bank to install a later version of purify if I know it will address the problem. If the later release doesn't address/fix the problem and allow me to purify, then my gonads are going to end up in a jar of marmalade somewhere! :) :)


seriously though. Has anybody seen this before and if yes, have they seen the problem fixed with a version of purify later than the 2003 beta release.


thanks for the memories


GrahamO