From 8d8d3249669149a68f3250cb580d7bfa1dd101dc Mon Sep 17 00:00:00 2001 From: Reena Lee Date: Tue, 9 Jun 2009 16:04:20 -0700 Subject: [PATCH] Removed SDK add-on product specification parameters (likely will add a separate SDK add-on section in the future). Removed reference to stack tool in debugging section, which is an internal-only tool. --- pdk/docs/guide/build_new_device.jd | 20 -------------------- pdk/docs/guide/debugging_native.jd | 7 ------- 2 files changed, 27 deletions(-) diff --git a/pdk/docs/guide/build_new_device.jd b/pdk/docs/guide/build_new_device.jd index b21371d23..2e2b367f8 100755 --- a/pdk/docs/guide/build_new_device.jd +++ b/pdk/docs/guide/build_new_device.jd @@ -215,26 +215,6 @@ pdk.version=1.0 list of space-separated words for a given product - - PRODUCT_SDK_ADDON_NAME - - - - - PRODUCT_SDK_ADDON_COPY_FILES - - - - - PRODUCT_SDK_ADDON_COPY_MODULES - - - - - PRODUCT_SDK_ADDON_DOC_MODULE - - -

diff --git a/pdk/docs/guide/debugging_native.jd b/pdk/docs/guide/debugging_native.jd index 5f9f0f75c..6705766a8 100755 --- a/pdk/docs/guide/debugging_native.jd +++ b/pdk/docs/guide/debugging_native.jd @@ -298,13 +298,6 @@ pid: 373, tid: 401 >>> android.content.providers.pim <<< 5300fc5c pthread_create system/klibc/android/pthread.c:182 -

If you save the debug spew into a file called out.txt, you can pass that to the tool, like this: -

- -
-./tools/stack out.txt
-
-

Or you can run logcat without any parameters and it will read from stdin. You can then paste output into the terminal or pipe it. Run logcat from the top of the tree in the environment in which you do builds so that the application can determine relative paths to the toolchain to use to decode the object files.