runtime: android backtraces do not include go backtrace

[zx2c4]

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.

[ALTree]

Possibly a dup of #22716?

[gwik]

@zx2c4 I added a comment to #22716 that relates to your problem.

[zx2c4]

Not quite the same thing here.

[FiloSottile]

/cc @eliasnaur

[cmcewen]

We are also having this issue. Any ideas on where to look to try and get more information?

[eliasnaur]

Related: #28997

[ashishb]

@zx2c4 On Android, I was able to collect the stack traces as well as logcat logs immediately after the golang crash using https://github.com/ivanarh/jndcrash

This hopefully should be sufficient for you as well.

[alalamav]

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?

[ashishb]

@alalamav, IMHO, this is specific to gomobile.

[zx2c4]

I wonder if it'd be possible for the Go crash handler to synthesize a fake call stack using the native ABI before aborting so that the default Play Store reporter gets useful information. (I'm not super keen on adding additional telemetry to my app to phone that home elsewhere.)

[ignoramous]

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?

Does jndcrash write stacktraces to DropBox or ALog to have it picked up presumably by Google on OHA-approved Androids? The ndcrash readme points out that the app has to send the stacktraces (to where ever) if it must.

I wonder if it'd be possible for the Go crash handler to synthesize a fake call stack using the native ABI

I am not sure what this alludes to, but would setting GOTRACEBACK=crash (goenv) work?