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. […]
troubleshooting
As you know, there are LIMIT settings in Linux OS which may have something to do with some frequent-happen-issue. Such as stack size, open files, core file generation, etc. Here are some tips about ulimit, core, and some debugging tricks relevant. 1. ulimit comamnd —————————— To view your OS limitations, […]
Debugging & troubleshooting tutorial: core dump debug
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, […]
Debugging & troubleshooting tutorial: backtrace + addr2line

Being a networking related product developer, we always face issues which can not be easily reproducted in LAB(because in most cases we have LAN only environments). Here I introduce you a tool, WANem – a WAN emulator tool from TATA. And we can benifit a lot in reproducing issues or […]
A Simple Tutorial for WANem

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. […]
How to get Callstack in Android Log File
Issue: #ping xxxx connect: No buffer space available #dmesg Neighbour table overflow messages.