Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
x/mobile: loading libgojni.so prevents android errors from printing to logcat #9482
Given a libgojni.so that is loaded via
I've seen this behavior using the v7 RecyclerView and not setting a layout manager which would normally print an error to logcat and exit. Instead, the go runtime starts and is followed by a WIN DEATH and nothing is printed in regards to the RecyclerView error.
I can put together a minimal sample upon request if the above is not clear enough.
Here is a minimal sample application with the libgojni.so already built: https://github.com/dskinner/go.issue.9482
Built with go at 6ceb604
Tested on a Nexus 10 running Android 5.0.1
This line is intentionally commented out to produce an error: https://github.com/dskinner/go.issue.9482/blob/master/app/src/main/java/cc/dasa/sample/MainActivity.java#L19
In the repo, the shared library is not loaded as can be seen here: https://github.com/dskinner/go.issue.9482/blob/master/app/src/main/java/cc/dasa/sample/App.java#L11
This produces the following stack trace as expected
Once this line is uncommented: https://github.com/dskinner/go.issue.9482/blob/master/app/src/main/java/cc/dasa/sample/App.java#L11
Launching the application produces the following output:
Noticeably, the stacktrace for the recyclerview error is lacking above.
It's worth noting I suppose that setting the layoutmanager for recyclerview and loading the libgojni.so does allow the application to launch successfully.