I've been working this all morning, but have to step out for a bit now.
This is the short short version of what I have found so far:
- This affects all stack protector values on aarch64, not just
-stack-protector 2. It is easier to trigger with 2 because it maps to
-fstack-protect
I will have some time to look into this later this week. It looks like
this is just libunwind expecting something to be present that isn't, but
I am not sure what the best way to fix it would be.
Thanks!
Todd
On Tue, Jul 13, 2021 at 04:50:54PM +, Charlene Wendling wrote:
> Hi,
>
> The edito
