History log of /frameworks/compile/libbcc/gdb_plugin/android-commands.py
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
cb2d2e7a169b376f93f7fd24fc0f79d90d6160d4 19-Jun-2014 Brian Carlstrom <bdc@google.com> Replace libdvm reference with libart

Bug: 14298175
Change-Id: I661e3dcd36c473d9c3224c09735bf2f601134736
/frameworks/compile/libbcc/gdb_plugin/android-commands.py
a663b778625f3de523e251ca810f4dc722c706be 03-Apr-2012 Stephen Hines <srhines@google.com> Translate x86->ARM + AOSP->JellyBean for RS debugging.

Change-Id: Ib7890840f8a3b96080af069547c0181b94ddf705
/frameworks/compile/libbcc/gdb_plugin/android-commands.py
094881f513ab366f7ffd0b2c7778ab50281ca59e 14-Dec-2011 Daniel Malea <daniel.malea@intel.com> Enable debugging of RS code under GDB

- Add/integrate GDBJITRegistrar support class for interfacing with GDB
-- Once the GDBJITRegistrar is merged into LLVM trunk (and AOSP upgrades LLVM)
all files GDB* should be removed, and replaced with appropriate includes

- Basic [host|target]-side integration tests
-- host-tests: use bcc driver and clang to verify gdb output
-- target-tests: run skeleton apk on target and verify gdb output

- Add support for optimization_level metadata in bcinfo, libbcc
-- Disabled some LTO passes when optimization_level = 0
-- move register allocator registration after metadata inspection

- Initial version of android-commands.py GDB plugin (for test infrastructure)
-- relevant commands: load-android-app, run-android-app, start-android-app
-- tested versions: gdb (7.2, 7.3), python (2.6, 2.7)

- build 'bcc' driver tool by default in eng builds

Change-Id: I99e0c11c8591c6d911632c1dcc82dd8fbe1244a8
/frameworks/compile/libbcc/gdb_plugin/android-commands.py