We've seen plenty of AFs where stack traces are incomplete or broken. In many or most cases, this appears to be an issue with the stack memory being corrupted in some way, not with the stack tracing library we use. Come up with some way to get information in the logs when stack frames are broken.

Note that this logging should only fire if

• We've attempted to get a stack trace the normal way and the output seems off.
• The trigger for the stack trace was a SEGV.

Unless both these conditions apply, limit ourselves to normal logging.