The android native backtrace always goes back to the abort() call, and does not include the more useful go backtrace. Therefore, in the Google Play Console, we're left with very unhelpful backtraces like:
It would be useful to have the backtrace here include information from Go's backtrace.
The text was updated successfully, but these errors were encountered:
I am also seeing this issue with a library built with gomobile. I was able to get a fully symbolicated stack trace in logcat by forcing a panic in the library. The stack trace is shown regardless of the linker flags used to build the binary (i.e. -ldflags '-s -w').
Is this an issue affecting all libraries built with NDK, or is it specific to gomobile? In other words, is it necessary to integrate a solution like the one described by @ashishb for the stack traces of (non-go) NDK libraries to show up in Google Play Console?