mumushou

专注于android中上层开发,app、framework。。

NDK Stack

python hy.panic.py error.txt


-----------------

英文文档见android-ndk-r6b的documentation.html

属于Android Native Development Kit (NDK)的一部分

http://developer.android.com/sdk/ndk/index.html

翻译仅个人见解

-----------------

 

Android ndk-stack tool

 

Android ndk-stack工具

----------------------

 

Introduction:

 

介绍:

-------------

 

This document describes the 'ndk-stack' tool that is distributed with the Android NDK, since release r6.

 

本文档描述ndk-stack工具,它从发布版r6开始由Anroid NDK分发。

 

Overview:

 

概述:

---------

 

'ndk-stack' is a simple tool that allows you to filter stack traces as they appear in the output of 'adb logcat' and replace any address inside a shared library with the corresponding : values.

 

ndk-stack是一个简单工具,允许你过滤在adb logcat输出中显示的堆栈跟踪,并且把共享库内的任意地址替换成相应的冒号值(注:这里应该指<函数名><文件名>:<行号>格式,见下)

 

In a nutshell, it will translate something like:

 

简而言之,它将翻译好像这样子的东西:

 

    I/DEBUG   (   31): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

    I/DEBUG   (   31): Build fingerprint: 'generic/google_sdk/generic/:2.2/FRF91/43546:eng/test-keys'

    I/DEBUG   (   31): pid: 351, tid: 351  %gt;%gt;%gt; /data/local/ndk-tests/crasher <<<

    I/DEBUG   (   31): signal 11 (SIGSEGV), fault addr 0d9f00d8

    I/DEBUG   (   31):  r0 0000af88  r1 0000a008  r2 baadf00d  r3 0d9f00d8

    I/DEBUG   (   31):  r4 00000004  r5 0000a008  r6 0000af88  r7 00013c44

    I/DEBUG   (   31):  r8 00000000  r9 00000000  10 00000000  fp 00000000

    I/DEBUG   (   31):  ip 0000959c  sp be956cc8  lr 00008403  pc 0000841e  cpsr 60000030

    I/DEBUG   (   31):          #00  pc 0000841e  /data/local/ndk-tests/crasher

    I/DEBUG   (   31):          #01  pc 000083fe  /data/local/ndk-tests/crasher

    I/DEBUG   (   31):          #02  pc 000083f6  /data/local/ndk-tests/crasher

    I/DEBUG   (   31):          #03  pc 000191ac  /system/lib/libc.so

    I/DEBUG   (   31):          #04  pc 000083ea  /data/local/ndk-tests/crasher

    I/DEBUG   (   31):          #05  pc 00008458  /data/local/ndk-tests/crasher

    I/DEBUG   (   31):          #06  pc 0000d362  /system/lib/libc.so

    I/DEBUG   (   31):

 

Into the more readable output:

 

变成更可读的输出:

 

    ********** Crash dump: **********

    Build fingerprint: 'generic/google_sdk/generic/:2.2/FRF91/43546:eng/test-keys'

    pid: 351, tid: 351  >>> /data/local/ndk-tests/crasher <<<

    signal 11 (SIGSEGV), fault addr 0d9f00d8

    Stack frame #00  pc 0000841e  /data/local/ndk-tests/crasher : Routine zoo in /tmp/foo/crasher/jni/zoo.c:13

    Stack frame #01  pc 000083fe  /data/local/ndk-tests/crasher : Routine bar in /tmp/foo/crasher/jni/bar.c:5

    Stack frame #02  pc 000083f6  /data/local/ndk-tests/crasher : Routine my_comparison in /tmp/foo/crasher/jni/foo.c:9

    Stack frame #03  pc 000191ac  /system/lib/libc.so

    Stack frame #04  pc 000083ea  /data/local/ndk-tests/crasher : Routine foo in /tmp/foo/crasher/jni/foo.c:14

    Stack frame #05  pc 00008458  /data/local/ndk-tests/crasher : Routine main in /tmp/foo/crasher/jni/main.c:19

    Stack frame #06  pc 0000d362  /system/lib/libc.so

 

Usage:

 

使用方法:

------

 

To do this, you will first need a directory containing symbolic versions of your application's shared libraries. If you use the NDK build system (i.e. ndk-build), then these are always located under $PROJECT_PATH/obj/local/<ab>, where <ab> stands for your device's ABI (i.e. 'armeabi' by default).

 

要做到这一点,你将首先需要一个包含你的应用程序的带符号版本的动态库的目录。如果你使用NDK构建系统(即ndk-build),那么它们总是位于$PROJECT_PATH/obj/local/<ab>目录下,这里<ab>是你的设备的ABI名称(即,默认是armeabi)。

 

You can feed the logcat text either as direct input to the program, e.g.:

 

你可以把logcat的文本作为直接的输入传给ndk-stack程序,例如:

 

   adb logcat | $NDK/ndk-stack -sym $PROJECT_PATH/obj/local/armeabi

 

Or you can use the -dump option to specify the logcat as an input file, e.g.:

 

或者你可以使用-dump开关指定logcat的输入文件,例如:

 

   adb logcat > /tmp/foo.txt

   $NDK/ndk-stack -sym $PROJECT_PATH/obj/local/armeabi -dump foo.txt

 

 

** IMPORTANT **:

 

** 重要事项 **:

 

  The tool looks for the initial line containing starts in the logcat output, i.e. something that looks like:

 

  这个工具会在logcat的输出内容中寻找包含开始内容的初始行,例如,如下所示的东西

 

    *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

 

  When copy/pasting traces, don't forget this line from the traces, or ndk-stack won't work correctly.

 

  当复制/粘贴追踪内容,不要忘记追踪中的这一行,否则ndk-stack将不能正确工作。

 

TODO:

 

待完成:

-----

 

A future version of 'ndk-stack' will try to launch 'adb logcat' and select the library path automatically. For now, you'll have to do these steps manually.

 

未来的ndk-stack版本将尝试启动adb logcat并且自动地选择库目录。现在,你不得不手动地做这些步骤。

 

As of now, ndk-stack doesn't handle libraries that don't have debug information in them. It may be useful to try to detect the nearest function entry point to a given PC address (e.g. as in the libc.so example above).

 

到现在为止,ndk-stack不会去处理不带调试信息的库。它可能对尝试检测离给定PC地址最近的函数入口点有用(例如,上面例子中的libc.so)


转自:http://weimingtom.iteye.com/blog/1167797

阅读更多
个人分类: android系统相关
想对作者说点什么? 我来说一句

android ndk-stack使用说明。

2012年03月19日 570B 下载

没有更多推荐了,返回首页

加入CSDN,享受更精准的内容推荐,与500万程序员共同成长!
关闭
关闭