Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

runtime: android backtraces do not include go backtrace #25035

Open
zx2c4 opened this issue Apr 24, 2018 · 9 comments

Comments

Projects
None yet
8 participants
@zx2c4
Copy link
Contributor

commented Apr 24, 2018

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:

image

It would be useful to have the backtrace here include information from Go's backtrace.

@ALTree

This comment has been minimized.

Copy link
Member

commented Apr 24, 2018

Possibly a dup of #22716?

@gwik

This comment has been minimized.

Copy link
Contributor

commented Apr 24, 2018

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

@zx2c4

This comment has been minimized.

Copy link
Contributor Author

commented Apr 24, 2018

Not quite the same thing here.

@FiloSottile

This comment has been minimized.

Copy link
Member

commented Apr 24, 2018

@cmcewen

This comment has been minimized.

Copy link

commented Feb 25, 2019

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

screen shot 2019-02-25 at 10 53 54 am

@eliasnaur

This comment has been minimized.

Copy link
Contributor

commented Feb 25, 2019

Related: #28997

@ashishb

This comment has been minimized.

Copy link

commented Mar 5, 2019

@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

This comment has been minimized.

Copy link

commented May 22, 2019

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

This comment has been minimized.

Copy link

commented May 22, 2019

@alalamav, IMHO, this is specific to gomobile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.