The call8/add sequences in the new changes look like they should be no problem. Sorry to be so picky about not recognizing call8/sub.
As for the PPC implementation, I'm not in a position to judge it. PurifyPlus runs on PPC with AIX (no Power Linux at this time), but I'm not familiar with PPC assembly code or the PIC patterns our recognizer supports. However, as you now know, anything labeled as an "ugly hack" (as LPICmeup is) will be suspect. On AIX there is a feature that lets users exclude entire libraries, so if a customer has a problem with libcrypto they could just exclude it from Purify processing. When you exclude a library on AIX we don't instrument it at all. Naturally, this means we can't report memory errors that originate in that library, even if the root cause of the error is API abuse on the part of the caller. But at least the customer gets full checking on the rest of their program. (That feature is still experimental on Solaris and Linux, not yet fully supported.) Would you care to try it yourself? You can get a trial version of PurifyPlus for free and run it on your libcrypto test programs. This will tell you if we patched things correctly. The eval version is "limited functionality": it works the same way and reports the same errors as the full version, but doesn't give pinpoint accuracy in error reports. You don't see line numbers or complete call chains like you do with the full version. (For that we ask you to pay.) There's a big "Download trial" button here: http://www-01.ibm.com/software/awdtools/purifyplus/unix ... installing the trial is very easy, no need to set up a license server or any nonsense like that. -- Allan Pratt, [email protected] Rational software division of IBM ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
