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 · 7 comments

Comments

Projects
None yet
7 participants
@zx2c4
Copy link
Contributor

zx2c4 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

ALTree commented Apr 24, 2018

Possibly a dup of #22716?

@gwik

This comment has been minimized.

Copy link
Contributor

gwik 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

zx2c4 commented Apr 24, 2018

Not quite the same thing here.

@FiloSottile

This comment has been minimized.

Copy link
Member

FiloSottile commented Apr 24, 2018

@cmcewen

This comment has been minimized.

Copy link

cmcewen 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

eliasnaur commented Feb 25, 2019

Related: #28997

@ashishb

This comment has been minimized.

Copy link

ashishb 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.

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.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.