Book Image

Android NDK Beginner's Guide

By : Sylvain Ratabouil
Book Image

Android NDK Beginner's Guide

By: Sylvain Ratabouil

Overview of this book

<p>Android NDK is all about injecting high performance into your apps. Exploit the maximum power of these mobile devices using high-performance and portable code.</p> <p>This book will show you how to create C/C++ enabled applications and integrate them with Java. You will learn how to access native API and port libraries used in some of the most successful Android applications.</p> <p>Using this practical step-by-step tutorial, highlighted with comments and tricks, discover how to run C/C++ code embedded in a Java application or in a standalone application. You will create a real native application starting from project creation through to full implementation of native API and the porting of existing third-party libraries. You will discover OpenGL ES and OpenSL ES, which are becoming the new standard in mobility. You will also understand how to access keyboard and input peripherals and how to read accelerometer or orientation sensors.</p> <p>Finally, you will dive into more advanced topics such as debugging and troubleshooting applications. By the end of the book, you should know the key elements to enable you to start exploiting the power and portability of native code.</p>
Table of Contents (19 chapters)
Android NDK Beginner's Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Stack trace analysis


No need to lie. I know it happened. Do not be ashamed, it happened to all of us... your program crashed, without a reason! You think probably the device is getting old or Android is broken. We all made that reflection but ninety-nine percent of the time, we are the ones to blame!

Debuggers are the tremendous tool to look for problems in your code. But they work in real time when programs run. They assume you know where to look for. With problems that cannot be reproduced easily or that already happened, debuggers become sterile.

Hopefully, there is a solution: a few utilities embedded in the NDK help to analyse ARM stack traces. Let's see how they work.