From 9c14e0a7188598b78a03477b6981a91792b3a318 Mon Sep 17 00:00:00 2001
From: Andy McFadden <fadden@android.com>
Date: Wed, 13 May 2009 10:39:24 -0700
Subject: [PATCH] Added a note in response to external feedback.

---
 docs/porting-guide.html | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/porting-guide.html b/docs/porting-guide.html
index 8a05caa1f..fd028ccf9 100644
--- a/docs/porting-guide.html
+++ b/docs/porting-guide.html
@@ -334,6 +334,12 @@ Some instructions are replaced by <code>dexopt</code>, notably when
 that you are testing the basic form of the instruction, add the
 <code>--no-optimize</code> option.
 </p><p>
+There is no in-built instruction tracing mechanism.  If you want
+to know for sure that your implementation of an opcode handler
+is being used, the easiest approach is to insert a "printf"
+call.  For an example, look at <code>common_squeak</code> in
+<code>dalvik/vm/mterp/armv5te/footer.S</code>.
+</p><p>
 At some point you need to ensure that debuggers and profiling work with
 your interpreter.  The easiest way to do this is to simply connect a
 debugger or toggle profiling.  (A future test suite may include some
-- 
2.11.0