Crash log information

Crash log information

Hey guys, i have a couple of questions regarding an Intel crash on an Android application. This is a game made with Unity with native support for Intel with x86 libs. We load some of our own .so x86 libs as well on app boot, and the crash is on one of our libs.

The first question is, how is it possible that the crash log has the namespaces and function names instead of memory adresses if the libs have no symbols? Crashes on arme abi's normaly have something like [libName].[memoryAddress]

The second question would be, given the information, is it possible to pinpoint the crash line? What is "(json:2017)", can't be line 2017 because the file only has ~900 lines. I guest it could be a memory offset after the parseJson function.

java.lang.Error: FATAL EXCEPTION [UnityMain]
Unity version     : 5.4.2f2
Device model      : Acer A1-830
Device fingerprint: acer/a1-830_ww_gen1/ducati:4.2.2/JDQ39/eng.svnadmin.20140320.154115:user/release-keys
Caused by: java.lang.Error: signal 11 (SIGSEGV), code 128 (?), fault addr 00000000
Build fingerprint: 'acer/a1-830_ww_gen1/ducati:4.2.2/JDQ39/eng.svnadmin.20140320.154115:user/release-keys'
Revision: '0'
pid: 27122, tid: 27122, name: clip.bowmasters  >>> com.miniclip.bowmasters <<<
	at<char, std::__ndk1::char_traits<char>, std::__ndk1::allocator<char> > const&)(json:114)
	at<char, std::__ndk1::char_traits<char>, std::__ndk1::allocator<char> > const&)(Postman:177)
	at<mc::HttpConnection const>, mc::Data const&, int)(Postman:155)
	at libmcservices.void std::__ndk1::__invoke_void_return_wrapper<void>::__call<mc::Postman::_httpSuccessCallback::{lambda(std::__ndk1::shared_ptr<mc::HttpConnection const>, mc::Data const&, int)#1}&, mc::HttpConnection const, mc::Data const, int>(mc::Postman::_httpSuccessCallback::{lambda(std::__ndk1::shared_ptr<mc::HttpConnection const>, mc::Data const&, int)#1}&, mc::HttpConnection const&&, mc::Data const&&, int&&)(__ndk1:119)
	at libmcservices.std::__ndk1::__function::__func<mc::Postman::_httpSuccessCallback::{lambda(std::__ndk1::shared_ptr<mc::HttpConnection const>, mc::Data const&, int)#1}, std::__ndk1::allocator<mc::Data const&>, void (mc::HttpConnection const, mc::Data const, int)>::operator()(mc::HttpConnection const&&, mc::Data const, int&&)(__ndk1:55)
	at libmcprime.0008dccb(Native Method)
	at libmcprime.00076799(Native Method)
	at libmcprime.Java_com_miniclip_utils_NativeRunnable_runNative(Java_com_miniclip_utils_NativeRunnable_runNative:42)
	at libdvm.dvmPlatformInvoke(dvmPlatformInvoke:80)
	at libdvm.dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)(dvmCallJNIMethod:580)
	at libdvm.dvmInterpret(Thread*, Method const*, JValue*)(dvmInterpret:204)

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px 'Helvetica Neue'; -webkit-text-stroke: #000000}
span.s1 {font-kerning: none}


3 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Is this post on the wrong section of the forum? 20 days without an useful answer...

Apologies - this forum has since been closed. But we obtained a response from an Intel expert for you:

"That is a hard one,

The best answer would require a specialist on Unity for Android and x86 to reply it and would demand some initial questions to understand the context better.

You will have better chances to get answers from the Unity forum:"

Best of luck with your issue.


Lexi S.
Intel® Software Developer Zone Support

Leave a Comment

Please sign in to add a comment. Not a member? Join today