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.
This commit is contained in:
Reena Lee
2009-06-09 16:04:20 -07:00
parent 1d7be8653c
commit 8d8d324966
2 changed files with 0 additions and 27 deletions

View File

@@ -215,26 +215,6 @@ pdk.version=1.0
<td valign="top">list of space-separated words for a given product</td>
<td valign="top"></td>
</tr>
<tr>
<td valign="top">PRODUCT_SDK_ADDON_NAME</td>
<td valign="top"></td>
<td valign="top"></td>
</tr>
<tr>
<td valign="top">PRODUCT_SDK_ADDON_COPY_FILES</td>
<td valign="top"></td>
<td valign="top"></td>
</tr>
<tr>
<td valign="top">PRODUCT_SDK_ADDON_COPY_MODULES</td>
<td valign="top"></td>
<td valign="top"></td>
</tr>
<tr>
<td valign="top">PRODUCT_SDK_ADDON_DOC_MODULE</td>
<td valign="top"></td>
<td valign="top"></td>
</tr>
</table>
</P>

View File

@@ -298,13 +298,6 @@ pid: 373, tid: 401 &gt;&gt;&gt; android.content.providers.pim &lt;&lt;&lt;
5300fc5c pthread_create system/klibc/android/pthread.c:182
</pre>
<p>If you save the debug spew into a file called <code>out.txt</code>, you can pass that to the tool, like this:
</p>
<pre class="prettify">
./tools/stack out.txt
</pre>
<p>Or you can run <code>logcat</code> without any parameters and it will read from <code>stdin</code>. You can then paste output into the terminal or pipe it. Run <code>logcat</code> 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.
</p>
</body>