When I run the the openssl evptest suite in purify runtime memory usage
analysis tool
it reports lots of memory segment errors in the AES crypto functions.
Question is how does purify calculate this segment boundary. Obviously
it doesn't look at current %esp value [as there are no references to
-N(%esp) in functions in question]. So how does it do it or rather is it
possible to confuse purify and make it miscalculate the boundary? Point
is that AES_[en|de]crypt allocates custom stack frame and aligns it in
very specific manner...
Is it possible to make purify point out offending instruction? Maybe
it's possible to make it dump the code instead of reporting error, in
which case you can use debugger to find the offending instruction... A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
