While investigating a deep stack (HELP-12717), we found that the libunwind printStackTrace implementation was doing its job and trying to give as much information as possible, but unfortunately this fills up the log statement 100k limit with just the raw instruction addrs, so all the good stuff in the stack trace is truncated. This is no good.

Easiest fix is to just not use libunwind's cursor steps, and just always do a rawBacktrace.