That may work for your own code which you can pepper with macros, but I needed to be able to capture crashes in native code I didn't write. Android itself has u

That may work for your own code which you can pepper with macros, but I needed to be able to capture crashes in native code I didn't write. Android itself has used a variety of unwinders over the years. Extracted versions of the libraries that have been modified to build with the NDK are here: https://github.com/ivanarh/libcorkscrew-ndk https://github.com/ivanarh/libcorkscrew-ndk https://github.com/ivanarh/libbacktrace-ndk https://github.com/ivanarh/libbacktrace-ndk https://github.com/ivanarh/libunwind-ndk https://github.com/ivanarh/libunwind-ndk https://github.com/ivanarh/libunwindstack-ndk https://github.com/ivanarh/libunwindstack-ndk Along with a wrapper that can use all of them: https://github.com/ivanarh/ndcrash https://github.com/ivanarh/ndcrash It's been a while since I dealt with this and I don't recall why Android keeps changing unwinders. Looks like Sentry is using libunwindstack-ndk (well a fork of it anyway) on Android: https://github.com/getsentry/sentry-native/tree/master/external https://github.com/getsentry/sentry-native/tree/master/exter...