summaryrefslogtreecommitdiffstats
path: root/dexdump
diff options
context:
space:
mode:
authorAndy McFadden <fadden@android.com>2009-10-28 17:39:02 -0700
committerAndy McFadden <fadden@android.com>2009-11-16 12:37:25 -0800
commit96516932f1557d8f48a8b2dbbb885af01a11ef6e (patch)
treea4bac9fd87ab5e88dfaaa92c84d99b6195fdc0fe /dexdump
parent62beb8b347e9e578de1844d56ce08f1d536e9c28 (diff)
downloadandroid_dalvik-96516932f1557d8f48a8b2dbbb885af01a11ef6e.tar.gz
android_dalvik-96516932f1557d8f48a8b2dbbb885af01a11ef6e.tar.bz2
android_dalvik-96516932f1557d8f48a8b2dbbb885af01a11ef6e.zip
Change the way breakpoints work.
This replaces the breakpoint mechanism with a more efficient approach. We now insert breakpoint instructions into the bytecode stream instead of maintaining a table. This requires mapping DEX files as private instead of shared, which allows copy-on-write to work. mprotect() is used to guard the pages against inadvertent writes. Unused opcode EC is now OP_BREAKPOINT. It's not recognized by dexdump or any interpreter except portdbg, but it can be encountered by the bytecode verifier (the debugger can request breakpoints in unverified code). Breakpoint changes are blocked while the verifier runs to avoid races. This eliminates method->debugBreakpointCount, which is no longer needed. (Also, it clashed with LinearAlloc's read-only mode.) The deferred verification error mechanism was using a code-copying approach to modify the bytecode stream. That has been changed to use the same copy-on-write modification mechanism. Also, normalized all PAGE_SIZE/PAGESIZE references to a single SYSTEM_PAGE_SIZE define. Simple Fibonacci computation test times (opal-eng): JIT, no debugger: 10.6ms Fast interp, no debugger: 36ms Portable interp, no debugger: 43.8ms ORIG debug interp, no breakpoints set: 458ms ORIG debug interp, breakpoint set nearby: 697ms NEW debug interp, no breakpoints set: 341ms NEW debug interp, breakpoints set nearby: 341ms Where "nearby" means there's a breakpoint in the method doing the computation that isn't actually hit -- the VM had an optimization where it flagged methods with breakpoints and skipped some of the processing when possible. The bottom line is that code should run noticeably faster while a debugger is attached.
Diffstat (limited to 'dexdump')
-rw-r--r--dexdump/OpCodeNames.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/dexdump/OpCodeNames.c b/dexdump/OpCodeNames.c
index 378dcf729..6a1a52a41 100644
--- a/dexdump/OpCodeNames.c
+++ b/dexdump/OpCodeNames.c
@@ -296,8 +296,8 @@ static const char* gOpNames[256] = {
"UNUSED",
"UNUSED",
"UNUSED",
- "UNUSED",
- "UNUSED",
+ "^breakpoint", // does not appear in DEX files
+ "^throw-verification-error", // does not appear in DEX files
"+execute-inline",
"UNUSED",