Hi all,
I'm trying to track down a bug in my own code using valgrind
and I've found something that I though I should report.
If I configure openssl-0.9.8e using:
./Configure linux-elf -DPURIFY -ggdb
and valgrind my program I get a couple of these reports:
==8577== Invalid write of size 4
==8577== at 0x80AF056: AES_cbc_encrypt (ax86-elf.s:1110)
==8577== Address 0xBE982280 is not stack'd, malloc'd or (recently) free'd
==8578==
==8578== Invalid write of size 4
==8578== at 0x80AF2DA: AES_cbc_encrypt (ax86-elf.s:1326)
==8578== Address 0xBE982E80 is just below the stack ptr.
==8577==
==8577== Invalid write of size 4
==8577== at 0x80AF2DA: AES_cbc_encrypt (ax86-elf.s:1326)
==8577== Address 0xBE982440 is not stack'd, malloc'd or (recently) free'd
<snip>
==8563== Invalid write of size 4
==8563== at 0x80AF056: AES_cbc_encrypt (ax86-elf.s:1110)
==8563== Address 0xBE980280 is not stack'd, malloc'd or (recently) free'd
==8563==
==8563== Invalid write of size 4
==8563== at 0x80AF2DA: AES_cbc_encrypt (ax86-elf.s:1326)
==8563== Address 0xBE980440 is not stack'd, malloc'd or (recently) free'd
The warnings reported seem to be in assembler code. If I then
configure with:
./Configure no-asm linux-elf -DPURIFY -ggdb
and recompile everything, the warnings above disappear. This seems
to suggest that there is an issue with the ASM versions of
AES_cbc_encrypt.
Cheers,
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo
+-----------------------------------------------------------+
"Code is more often read than written and thus making it
readable is more important than making it writable."
-- Marcin 'Qrczak' Kowalczyk
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
