This post’s goal is to guide a starter to analysis a crash by reading into the assemble code.
But the example listed here is not a good one, because the crash point is not an obvious one, the real reason of the crash for this example is still remain uncovered.
My point here is, we can use a such kind of way to analysis some crash, and once you read this post, you can start the first step. If you run into any problems when analysis your crash, well, we can discuss wih them together here. Here we go. Continue reading “Trouble shooting: step by step to analysis crashes”
Planning to write a series of posts about debugging & trouble shooting tricks. And I’d like to make backtrace as a start. As a typical programmer(AKA nerd), I’d like to jump to the topic directly before run into blah-blah.
Everyone knows, bug is free, so it may be at everywhere, to check out your free gift(s) sending to your clients, you may consider backtrace.
Continue reading “Debugging & troubleshooting tutorial: backtrace + addr2line”
When you are running into bugs or issues in you Android Apps, callstack information of your components would be very much helpful, defintely.
Here is a post I’v found in freescale community, auther by MingZhou, it instructs you have get the caller stack information for you Android App or components. The original url is: https://community.freescale.com/docs/DOC-93624
Continue reading “How to get Callstack in Android Log File”