|
Post by skaplon on Mar 19, 2019 12:25:50 GMT
Whats the correct way to report crashes in native code? We are getting many of these which I suppose the callstack doesn't help much, so how can we build the needed debug info to improve those? It seems google allows to upload symbol maps to get better callstacks
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
backtrace: #00 pc 0000000000239318 /data/app/com.wonder_sistemas.probusm2-lGSx6lQ3U48zSHitr-yf2w==/lib/arm/librhodes.so (_Z21js_s_NewORM_useNewOrmRKSsRN3rho4json10CJSONArrayES0_S0_S0_+452)
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
backtrace: #00 pc 0000000000641450 /data/app/com.wonder_sistemas.probusm2-1/lib/arm/librhodes.so (_ZN3rho6common10CRhodesApp12navigateBackEv+16)
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
#00 pc 0000000000239318 /data/app/com.wonder_sistemas.probusm2-X-qa1e6MewC9ofsJHclNtg==/lib/arm/librhodes.so (js_s_NewORM_useNewOrm(std::string const&, rho::json::CJSONArray&, std::string const&, std::string const&, std::string const&)+452)
|
|
|
Post by Alex Epifanov on Mar 20, 2019 14:02:29 GMT
You can get more verbose callstack if you set 'debug' build type in build.yml, and also build with rake device:android:debug command. If you have specific steps to reproduce the crash I can try to help. Seems you are calling NewORM API?
|
|