Sean Parkinson

Hi @calvin2021y Can you please confirm that the access violation in wc_AesInit() is at the line aes.c:10692: ``` aes->aadLen = 0; ``` If it is, then this is very strange...

Hi @calvin2021y Please make sure that you are linking against a wolfSSL library built with the same options that are used when building the application and/or library that uses wolfSSL....

Hi @calvin2021y, There have been fixes to the sp_arm64.c file since 5.5.4. Please use the latest version of sp_ar,64.c if possible. Could you apply the patch to the keys.c on...

Hi @calvin2021y, Can you please tell me what the line at aes.c:10692:17 looks like for you? Looking at v5.5.4-stable, the line is: ``` aes->aad_len = 0 ``` Also, keys.c:2487 This...

Hi @calvin2021y It appears it is the memseting of the aes->aadH that is the issue. Can you print out the address of aes->aadH before the XMEMSET? The Aes structure has...

Hi @calvin2021y Please put the print out into keys.c, instead of aes.c, before the call that crashed and let me know what happens. Thanks, Sean

Did the code crash this time> If not, then it appears to be a compiler bug. You may have to reduce the optimization level until the code works. Sean

Hi @calvin2021y, The compiler appears to be unstable from what I've seen here. What are the link errors when -O0? Sean

Hi @calvin2021y Please try -fno-inline with clang and let us know if that makes a difference. I believe that will stop inlining of functions like the wc_AesInit(). I've asked other...

Hi @calvin2021y I'm really frustrated by this one. Can I ask you to try one more thing? Your previous patch was: ``` diff --git a/wolfcrypt/src/aes.c b/wolfcrypt/src/aes.c index 63928bafe..341d6e765 100644 ---...