Nikos Mavrogiannopoulos nmav@gnutls.org writes:
It exits successfully but prints the valgrind warning (shown in the previous message).
Then I know what to expect.
Do you get a warning after applying the patch?
Haven't had time to try it yet.
I just had a look at x86_64/memxor.asm. As far as I see, it's written to not read anything outside of the input buffers. Initial and final portions are done with loops doing one byte at a time. It's not clear how it could read beyond the input area without also clobbering bytes outside of the destination area. Some debugging needed.
In the memxor tests, do you put the buffers at a zone exactly at the ending position of the buffer,
No. That's probably why valgrind doesn't warn about it. I just allocate a buffer of 16 + MAX_SIZE bytes, and try with starting address buf, buf+1, ..., buf + 15.
Regards, /Niels