Android native thread crash stack trace format interpretation

0

I have an android native thread crash stack trace, I don't understand the "+ 0xf" meaning in each frame, can someone give me an interpretation about it, and where I can learn more about it

Thread 28 (crashed)
0 libppcp.so!JniCallback [jni.h : 558 + 0x0]
fp = 0x00000054 sp = 0xc9f14b40 lr = 0xeae47f61 pc = 0xcaa4ac8e
Found by: given as instruction pointer in context
1 libppcp.so!CallBackToView::OnRecvData(int, std::string, std::string) [callback.cpp : 438 + 0x9]
Found by: call frame info
2 libppcp.so!chatroomInterface::onBackToView(int, std::string, std::string) [interfacemgr.cpp : 136 + 0xf]
Found by: call frame info
3 libchatroommgr.so!ChatroomProcessor::CallBackToView(int, std::string, std::string) [chatroomprocessor.cp p : 401 + 0x9]
4 libchatroommgr.so!ChatroomProcessor::HandleSERVERBroadCast(RCMMsg*) [chatroomprocessor_server.cpp : 1766 + 0xf]
5 libchatroommgr.so!ChatroomProcessor::CallProcess(RCMMsg*) [chatroomprocessor.cpp : 106 + 0x3]
6 libchatroommgr.so!ChatRoomTaskQueue::CallProcess() [chatroomtaskqueue.cpp : 53 + 0x7]
7 libchatroommgr.so!ChatRoomTaskQueue::Run() [chatroomtaskqueue.cpp : 74 + 0x5]
8 libchatroommgr.so!ChatRoomProcessThread::Thread() [chatroomprocessthread.cpp : 81 + 0x7]
r4= 0xca28b05c r5 = 0xca28b06c = 0xca28b060 r9 = 0xca28b05c = 0xc9f158e8 pc = 0xca23c0df
r6 = 0xca28b074 r7 = 0xc9f158f0 r10 = 0xdel75ded fp = 0x00000054

stack-trace
asked on Stack Overflow Nov 4, 2019 by money9bit

0 Answers

Nobody has answered this question yet.


User contributions licensed under CC BY-SA 3.0