Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#1326 closed Enhancement (fixed)

stack trace/debug output on Android if app crashes

Reported by: carlgt1 Owned by: carlgt1
Priority: Minor Milestone: Undetermined
Component: Manager - Android Version: 7.0.64
Keywords: Cc:

Description

the Android NDK (ie C/C++ libraries compiled for android) don't seem to provide much output on a crash (ie segfault etc). It seems that with the "Jelly Bean" Android (v 4.1) a lot of the facility for printing out a stack trace was removed. About the only avenue left is using the "CallStack?" class in the shared library (which seems to be in all Android distros/versions) -- libutils.so. Unfortunately, after figuring out how to use this class "CallStack?" -- the output is not very good, just one line printed with an unknown address and the calling program (not even the calling routine/function). I will attach my results to this ticket. I'm not sure if it's worth incorporating into BOINC (just a few lines in lib/diagnostics.cpp) since the output from Android is so poor.

Attachments (1)

boinc_lib_android_stacktrace.zip (170.9 KB) - added by carlgt1 11 years ago.
mods to boinc/lib/ and include files for Android "CallStack?" (libutils.so) for stack trace upon a crash

Download all attachments as: .zip

Change History (3)

Changed 11 years ago by carlgt1

mods to boinc/lib/ and include files for Android "CallStack?" (libutils.so) for stack trace upon a crash

comment:1 Changed 11 years ago by carlgt1

Resolution: fixed
Status: newclosed

comment:2 in reply to:  description Changed 11 years ago by carlgt1

NB: I'll leave open in case someone else wants to look into it -- I spent a few days on this and don't see any way to get more output from Android -- it seems they (google) want people to just put in their own try-catch blocks all over to trap crashes and not rely on traditional stack traces etc.

Note: See TracTickets for help on using tickets.