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.
Hi,
BTW, have you considered synergetic implementation, which would work as
following. Arrange an intermediate buffer followed by non-accessible
page [commonly would be done with anonymous mmap of two pages followed
by mprotect(PROT_NONE) for the second page]. Upon *_init we call
software
Hi,
I've just tried compiling OpenSSL-0.9.8a for HPPA64 architecture
(using gcc-4.1) and 'make test' ends with
...
ecb idea ok
cbc idea ok
cfb64 idea ok
../util/shlib_wrap.sh ./shatest
*** Termination signal 139
Stop.
*** Error exit code 1
Stop.
Any
Hi,
several users have complained that the padlock engine is not usable in
new distros like Fedora 5 or OpenSUSE 10.1 that come with 0.9.8a. There
was apparently some reorganization of engines to dynamically loadable
modules. I haven't followed OpenSSL development for a while, could you
give be a
Has using a different compiler been suggested already?
Any suggestions for the newest gcc that's known to work? 3.4.5?
I'm using one of HP's Testdrive machines for building, so I suppose
building several compilers wouldn't be appreciated too much, especially
since the 4.1.0 that's causing
Hi,
so I didn't really think of using HP's compiler.
Well, using HP's compiler, I get an OpenSSL version which does
successfully pass the make test command...
Looks more and more like a bug in gcc-4.1
Portable code is a chore ain't it :) It could be worse, you could be
trying to
