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
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...
Should read dump the core, not code. A.
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.
If I build openssl with AES assembler code disabled (e.i AES in c-code)
the same test
runs without any errors from purify.
The test was
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.
If I build openssl with AES assembler code disabled (e.i AES in c-code)
the same test
runs without any errors from purify.
Anyone seen
