Re: FYI: main (bad9fa56620e based): some unexpected SIGSEGV's are tied to interrupted system calls (cortex-a57/a72 fail, cortex-a53/cortex-a7 work)

On 2021-Mar-9, at 21:11, Mark Millard wrote: > On 2021-Mar-9, at 19:17, Mark Millard wrote: > > [My only testing context for this has been main, not 13.0. > But it might be a 13.0 worry.] > >> Using the quickest to so-far-reliably-fail type of example from >> another thread I used truss to see

Re: FYI: main (bad9fa56620e based): some unexpected SIGSEGV's are tied to interrupted system calls (cortex-a57/a72 fail, cortex-a53/cortex-a7 work)

On 2021-Mar-9, at 19:17, Mark Millard wrote: [My only testing context for this has been main, not 13.0. But it might be a 13.0 worry.] > Using the quickest to so-far-reliably-fail type of example from > another thread I used truss to see what happens, here filtered > down to two processes that a