> On Jun 13, 2018, at 12:31 PM, Michael Wojcik <Michael.Wojcik@xxxxxxxxxxxxxx> wrote: > > It's a c0000005 - an addressing violation - so there's a decent chance that it's raised in or near (in terms of stack frames) where the actual cause exists in the code. Perhaps a memory alignment issue, that is somewhat peculiar to the SOC in question. I'd try a non ASM build, and if that passes, look for changes in the ASM code, or changes in the build flags. -- Viktor. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
