| 75978b1e139da312515ec07022d47ac615615d1b |
16-Jul-2013 |
Elliott Hughes <enh@google.com> |
Remove an assertion that JDWP packets are small.
Now we support longer allocation tracker runs, it's possible
to collect more than 1MiB of data.
Bug: 9871848
Change-Id: Ifb575538b97563ce909f7e0aa6840ccbd6e93569
dwpHandler.cpp
|
| b680ae3140a789f182c26abf8df9645f7744113a |
17-Apr-2013 |
Elliott Hughes <enh@google.com> |
Work around a dalvik JDWP/GC deadlock.
Also add a few missing TEMP_FAILURE_RETRYs that can cause dalvik to
incorrectly decide that the debugger connection has been broken.
Bug: 8191824
Change-Id: I791b514c6bec1ca634a65d9f87c5fa06da01b5ed
dwpAdb.cpp
dwpMain.cpp
dwpSocket.cpp
|
| b825d9f38b6359ec2ac23528ac0342838e1f152f |
02-Apr-2013 |
You Kim <you.kim72@gmail.com> |
Fix a minor leak in handleVM_CreateString
Change-Id: I3273e5d2eb4621202837c43270a466fe056d6894
dwpHandler.cpp
|
| bb046193c2da5d43a57b2fa8a17a0f634bf003ba |
07-Aug-2012 |
Elliott Hughes <enh@google.com> |
Fix ALOGV bit rot.
Change-Id: Ia182af8f5ca3967a21003b3d1513145f8e6e5db0
dwpHandler.cpp
|
| 9bffe7cc708802f20bd8790c99cc68a6b721eba8 |
28-Mar-2012 |
Elliott Hughes <enh@google.com> |
am b9f5c7aa: am 3ddb30bd: am 6bcf5d20: Merge "Obvious mix of = and =="
* commit 'b9f5c7aa88c3c731501bd1c61baefa5c761947a1':
Obvious mix of = and ==
|
| fa76cb555c1683d36ef9d6f6680a0e4e16115679 |
27-Mar-2012 |
Mark Gordon <msg555@gmail.com> |
Obvious mix of = and ==
Change-Id: I52183924c287b80e9ca7c20df6edfe132b43e088
dwpEvent.cpp
|
| b74e7190e86d559712747e5cdb31a0d390b7af7d |
16-Feb-2012 |
Iliyan Malchev <malchev@google.com> |
Replace malloc() followed by memset() to zero with calloc()
Bionic's calloc() is smart enough to not zero out memory if it gets that memory
from an anonyous mmap. Thus, if we use malloc for large allocations, we cause
unnecessary memory duplication by following the malloc() with a memset().
An even better approach would be to replace the known large calloc() calls with
dvmAllocRegion() allocation.
Change-Id: Id308f541c9a040d5929bf991b6c2bfdefb823c3c
dwpEvent.cpp
|
| 5da436293b72a28b46a47fb863e1146f3baef42f |
27-Jan-2012 |
Andy McFadden <fadden@android.com> |
Fix assert
Change-Id: If764fe38e215473590a6fe6be910827a38382054
dwpMain.cpp
|
| c1a4ab9c313d8a3d12007f2dbef7b5a6fa4ac2ef |
06-Jan-2012 |
Steve Block <steveblock@google.com> |
Rename (IF_)LOGE(_IF) to (IF_)ALOGE(_IF) DO NOT MERGE
See https://android-git.corp.google.com/g/#/c/157220
Also fix an occurrence of LOGW missed in an earlier change.
Bug: 5449033
Change-Id: I2e3b23839e6dcd09015d6402280e9300c75e3406
xpandBuf.cpp
dwpAdb.cpp
dwpEvent.cpp
dwpHandler.cpp
dwpMain.cpp
dwpSocket.cpp
|
| e8e1ddccd616e8226b7cc1e4e9fdb327429249e8 |
06-Jan-2012 |
Steve Block <steveblock@google.com> |
Rename (IF_)LOGW(_IF) to (IF_)ALOGW(_IF) DO NOT MERGE
See https://android-git.corp.google.com/g/157065
Bug: 5449033
Change-Id: Ia5d301248024df26c2a29dabdfe738e39ec87c82
dwpAdb.cpp
dwpEvent.cpp
dwpHandler.cpp
dwpMain.cpp
dwpSocket.cpp
|
| 4308417beec548c2b2c06ecec4f7f4a965b09fb2 |
04-Jan-2012 |
Steve Block <steveblock@google.com> |
Rename (IF_)LOGI(_IF) to (IF_)ALOGI(_IF) DO NOT MERGE
See https://android-git.corp.google.com/g/156801
Bug: 5449033
Change-Id: Ic558031c75b3702d90eb78bd730501ae5d3c077b
dwpAdb.cpp
dwpEvent.cpp
dwpHandler.cpp
dwpMain.cpp
dwpSocket.cpp
|
| 062bf509a77fce9dfcb7e7b2e401cf2a124d83d5 |
20-Dec-2011 |
Steve Block <steveblock@google.com> |
Rename (IF_)LOGD(_IF) to (IF_)ALOGD(_IF) DO NOT MERGE
See https://android-git.corp.google.com/g/156016
Bug: 5449033
Change-Id: Ic663376d1ad6a6cb14bf81405ad9afd247cf2f60
dwpAdb.cpp
dwpEvent.cpp
dwpMain.cpp
dwpSocket.cpp
|
| 92c1f6f1b4249e4e379452ee7b49f027052bf4ce |
20-Oct-2011 |
Steve Block <steveblock@google.com> |
Rename (IF_)LOGV(_IF) to (IF_)ALOGV(_IF) DO NOT MERGE
See https://android-git.corp.google.com/g/#/c/143865
Bug: 5449033
Change-Id: I8bd96961e369a08e86ff78b82d90f20f42787eb1
dwpAdb.cpp
dwpEvent.cpp
dwpHandler.cpp
dwpMain.cpp
dwpSocket.cpp
|
| 1663a6c12fdf4732d7ea0a0406af6085b3c408e4 |
12-Oct-2011 |
Steve Block <steveblock@google.com> |
Rename (IF_)LOG() to (IF_)ALOG() DO NOT MERGE
See https://android-git.corp.google.com/g/#/c/141576
Bug: 5449033
Change-Id: Ie3bc0d5436218ea05f98cb0373ecf5924f78db05
dwpHandler.cpp
|
| db57ab15e5235d9ec916464d5c54452c99508c2c |
27-Jul-2011 |
Mike Lockwood <lockwood@android.com> |
Remove "adbd disconnected" log spam
Change-Id: I532433a5ee3f23bad8dc5fdb0f398253f2b6eb8b
Signed-off-by: Mike Lockwood <lockwood@android.com>
dwpAdb.cpp
|
| 128689844fda7f9287cc7494ec357397b6d59576 |
01-Jul-2011 |
jeffhao <jeffhao@google.com> |
Added mutex for jdwp socket writes to prevent interleaving.
This commit includes a following change: Clean up jdwp adb/socket
and fix initialization issues.
Change-Id: I79461b92d690e42d8d1d82d31fbcacb4d5650a74
dwpAdb.cpp
dwpMain.cpp
dwpPriv.h
dwpSocket.cpp
|
| 8bd8e5ba33a920a1dbad67b390e316ac0aebb0bb |
25-Jun-2011 |
Doug Kwan <dougkwan@google.com> |
Merge "Fix gcc-4.6 warnings."
|
| 7a921948c597d72a6db9ec6f3a0f1fbdfd3e49c8 |
25-Jun-2011 |
Doug Kwan <dougkwan@google.com> |
Fix gcc-4.6 warnings.
Change-Id: I62cfb8b1a39499366ee18c1904e6991567f78571
dwpConstants.cpp
dwpConstants.h
|
| 29527c9db5fcaac8ae4c567304d8b7160110214b |
24-Jun-2011 |
Brett Chabot <brettchabot@android.com> |
Fix for adb shell hang after adb root.
Abort JDWP thread if netstate is shutting down.
Bug 4731499
Change-Id: I4e1ec9cf64d00682b1dd10e448c3665a4fc77ba8
dwpAdb.cpp
|
| 375fb116bcb817b37509ab579dbd55cdbb765cbf |
15-Jun-2011 |
Carl Shapiro <cshapiro@google.com> |
Normalize the include guard style.
An leading underscore followed by a capital letter is a reserved
name space in C and C++.
This change also moves any #include directives within the include
guard in some of the compiler/codegen/arm header files.
Change-Id: I9715e2c5301699d31886e61d0fe6e29483555a2a
xpandBuf.h
dwp.h
dwpConstants.h
dwpEvent.h
dwpHandler.h
dwpPriv.h
|
| 291c84f60853d30e1c0d79dd08c5e5164f588e26 |
26-May-2011 |
Dan Bornstein <danfuzz@android.com> |
Prefer printf format "%#x" over "0x%x".
I exist to serve.
Change-Id: I8e2880b20eefd466da8515d5b6b0c5cb75d56169
dwpHandler.cpp
|
| 60fc806b679a3655c228b4093058c59941a49cfe |
26-May-2011 |
Dan Bornstein <danfuzz@android.com> |
Further conservation of newlines.
Friends don't let friends end LOG() strings with newlines.
Change-Id: I5a18c766c90c4ab5f03caa6acd601d34d91beb00
xpandBuf.cpp
dwpAdb.cpp
dwpEvent.cpp
dwpHandler.cpp
dwpMain.cpp
dwpSocket.cpp
|
| d53c7efac74f2c690a86871f160a0f36fbc069ef |
13-May-2011 |
Dan Bornstein <danfuzz@android.com> |
Address CVE-2011-1090.
This adds a credentials check after connecting to the (alleged)
ADB control socket, to make sure that the other side really is
the system and not a malicious non-system process.
Since I was in the territory, I also did some minor comment
cleanup / correction (at the top of the file).
This change relies on a related change in system/core.
Change-Id: Iecbc4383cf285444f9d5a0414986951593777fa3
dwpAdb.cpp
|
| d862faa2ceae186da5518607505eb942d634ced9 |
28-Apr-2011 |
Carl Shapiro <cshapiro@google.com> |
Get rid of uneeded extern, enum, typedef and struct qualifiers.
Change-Id: I236c5a1553a51f82c9bc3eaaab042046c854d3b4
xpandBuf.h
dwp.h
dwpConstants.cpp
dwpConstants.h
dwpEvent.cpp
dwpEvent.h
dwpHandler.cpp
dwpHandler.h
dwpPriv.h
|
| 1e1433e78f560a01744e870c19c162ab88df9dc1 |
21-Apr-2011 |
Carl Shapiro <cshapiro@google.com> |
Remove unneeded void argument list declarations.
Change-Id: Ica749f6defa890363ec531b29e25bc415dc2cbb9
xpandBuf.cpp
dwpAdb.cpp
dwpEvent.cpp
dwpMain.cpp
dwpSocket.cpp
|
| d5c36b9040bd26a81219a7f399513526f9b46324 |
16-Apr-2011 |
Carl Shapiro <cshapiro@google.com> |
Move the remaining non-compiler VM code into C++.
Change-Id: Id8693208d2741c55a7b0474d1264f2112019d11f
dwpAdb.cpp
|
| 2d63bc57d5fcbcd54f0bd3e9491e1704b98ec0bf |
14-Apr-2011 |
Carl Shapiro <cshapiro@google.com> |
Move JDWP into C++ and add extern "C" to remaining non-compiler includes.
Change-Id: I19cba56e8f75b76f902c87ff5c5b3e2c17cb5c00
xpandBuf.c
xpandBuf.cpp
xpandBuf.h
dwp.h
dwpAdb.c
dwpAdb.cpp
dwpConstants.c
dwpConstants.cpp
dwpConstants.h
dwpEvent.c
dwpEvent.cpp
dwpEvent.h
dwpHandler.c
dwpHandler.cpp
dwpHandler.h
dwpMain.c
dwpMain.cpp
dwpPriv.h
dwpSocket.c
dwpSocket.cpp
|
| 9a3147c7412f4794434b4c2604aa2ba784867774 |
03-Mar-2011 |
buzbee <buzbee@google.com> |
Interpreter restructuring
This is a restructuring of the Dalvik ARM and x86 interpreters:
o Combine the old portstd and portdbg interpreters into a single
portable interpreter.
o Add debug/profiling support to the fast (mterp) interpreters.
o Delete old mechansim of switching between interpreters. Now, once
you choose an interpreter at startup, you stick with it.
o Allow JIT to co-exist with profiling & debugging (necessary for
first-class support of debugging with the JIT active).
o Adds single-step capability to the fast assembly interpreters without
slowing them down (and, in fact, measurably improves their performance).
o Remove old "polling for safe point" mechanism. Breakouts now achieved
via modifying base of interpreter handler table.
o Simplify interpeter control mechanism.
o Allow thread-granularity control for profiling & debugging
The primary motivation behind this change was to improve the responsiveness
of debugging and profiling and to make it easier to add new debugging and
profiling capabilities in the future. Instead of always bailing out to the
slow debug portable interpreter, we can now stay in the fast interpreter.
A nice side effect of the change is that the fast interpreters
got a healthy speed boost because we were able to replace the
polling safepoint check that involved a dozen or so instructions
with a single table-base reload. When combined with the two earlier CLs
related to this restructuring, we show a 5.6% performance improvement
using libdvm_interp.so on the Checkers benchmark relative to Honeycomb.
Change-Id: I8d37e866b3618def4e582fc73f1cf69ffe428f3c
dwpMain.c
|
| 0970976b0e980be00424f93a69c2bc13ca3131f3 |
18-Mar-2011 |
Andy McFadden <fadden@android.com> |
Fix up some JDWP stuff
Notably:
- Claim to know about synthetic attributes (canGetSyntheticAttribute).
Set an appropriate flag in the access flags of fields and methods.
(Makes no difference that I can see in Eclipse.)
- Stop making copies of descriptor strings. That ceased to be necessary
after they were normalized in DEX (pre-1.0).
- Correct object type determination, especially w.r.t. the specially-
tagged types (strings, threads, classloaders, etc).
- Handle a FIELD_ONLY mod (not tested).
- Added a bit of debugging stuff.
Change-Id: I5651b5b76d904a9edbd051e039423795faaa1650
dwpConstants.c
dwpConstants.h
dwpEvent.c
dwpEvent.h
dwpHandler.c
|
| cb3081f675109049e63380170b60871e8275f9a8 |
14-Jan-2011 |
buzbee <buzbee@google.com> |
Consolidate mterp's debug/profile/suspend control
This is a step towards full debug & profiling support in JIT'd code.
Previously, the interpreter made multiple distinct checks for pending
suspend requests, debugger and profiler checks at each safe point.
This CL moves the individual controls into a single control word,
significantly speeding up the safe-point check code path in the common
fast case.
In short, any time some VM component wants control to break at a safe
point it will set a bit in gDvm.interpBreak, which will be examined
at the safe point check in footer.S. In the old code, the safe point
check consisted of 11 instructions (including 6 loads). The new sequence
is 6 instructions (4 loads - two of which are needed and two are
speculative to fill otherwise stalling slots).
This code path is hot enough in the interpreter that we actually see
some measureable speedups in benchmarks. The old sieve benchmark
improves from 252 to 256 (~1.5%).
As part of the change, global debuggerActive and activeProfilers variables
have been eliminated as redundant. Note also that there is a subtle
change in thread suspension. Thread suspend request counts are kept on
a per-thread basis, and previously each thread would only examine its own
suspend count. With this change, a bit has been allocated in interpBreak
to signify that at least one suspend request is active across all
threads. This bit is treated as "some thread is supposed to
suspend, check to see if it's me".
Change-Id: I527dc918f58d1486ef3324136080ef541a775ba8
dwpMain.c
|
| fc75f3ed87b55d625b6054e18645da5cbdba31c6 |
07-Dec-2010 |
Carl Shapiro <cshapiro@google.com> |
Fix implicit conversions, rename reserved works, enable -Wc++-compat.
Change-Id: I06292964a6882ea2d0c17c5c962db95e46b01543
xpandBuf.c
dwpAdb.c
|
| 2150b0d21e9db50d76628b6442616489d156b5ad |
15-Oct-2010 |
Andy McFadden <fadden@android.com> |
Switch to VMWAIT before sending to DDMS
If you stop DDMS with Ctrl-Z, packets sent from the VM will start
to back up and eventually the network write will block. The VM was
doing the write in "running" state, which meant that if another thread
tried to GC it would be unable to suspend the stalled thread and the
VM would abort.
Now when this happens the affected thread(s) will be quietly stuck until
DDMS is resumed. (We may want to fix that eventually.)
Bug 3101425.
Change-Id: Ide83c4622137e24c23ee85c006b497d84cf5006b
dwpEvent.c
|
| fc3d31683a0120ba005f45f98dcbe1001064dafb |
05-Aug-2010 |
Andy McFadden <fadden@android.com> |
More SMP fixes.
Convert some ANDROID_MEMBAR_FULL uses into equivalent atomic ops. A
couple of "bool" had to convert to "int" since we don't have atomic
ops for bools.
Replaced a local implementation of atomic inc with a call to the
atomic inc function.
Change-Id: I948b8080d743552bde014d3a6e716ed2c30ebef8
dwpMain.c
dwpPriv.h
|
| 884cd427f504a6e105059199c3eeadd51a8b9c6e |
19-Jul-2010 |
Andy McFadden <fadden@android.com> |
Implement JDWP ArrayType.NewInstance.
With this, you can go into the Eclipse "Display" view and evaluate
"new byte[5]" to get "(byte[]) [0, 0, 0, 0, 0]".
Change-Id: Id110c5701a9de12222760be6623585b5f7e28023
dwpHandler.c
|
| deeeeb264fc6f4ab7f5cb6e01b9dd76f487ff914 |
16-Jun-2010 |
Andy McFadden <fadden@android.com> |
Dalvik SMP update
Fix some SMP correctness issues in the VM:
- Correct AtomicCache implementation, inserting barriers where needed
and correcting existing usage.
- Emphasize that String startup isn't expected to be reentrant, and
use atomic ops to ensure that we explode if anybody tries it.
- Use 64-bit quasiatomic ops to manage the "last activity" timer in
JDWP. (Also, provide some documented but unimplemented behavior.)
- Updated the volatile operations in sun.misc.Unsafe to include
appropriate barriers.
(This does not purport to correct all SMP issues, just some of the
more obvious ones.)
Change-Id: I06957ebcf2724fe7a228b30d00194b9b4808fae0
dwpHandler.c
dwpMain.c
dwpPriv.h
|
| 6e10b9aaa72425a4825a25f0043533d0c6fdbba4 |
15-Jun-2010 |
Andy McFadden <fadden@android.com> |
Atomic op cleanup.
Replaced VM-local macros for barrier and CAS calls with the actual
versions provided by cutils.
ATOMIC_CMP_SWAP(addr,old,new) --> android_atomic_release_cas(old,new,addr)
MEM_BARRIER --> ANDROID_MEMBAR_FULL
Renamed android_quasiatomic* to dvmQuasiAtomic*.
Didn't change how anything works, just the names.
Change-Id: I8c68f28e1f7c9cb832183e0918d097dfe6a2cac8
dwpHandler.c
dwpMain.c
|
| 7365493ad8d360c1dcf9cd8b6eee62747af01cae |
09-Jun-2010 |
Carl Shapiro <cshapiro@google.com> |
Remove repeated newlines at the end of files.
Change-Id: I1e3d103a7b932ef21acedb6438c0f26b315df28f
xpandBuf.c
dwpAdb.c
dwpConstants.c
dwpEvent.c
dwpHandler.c
dwpMain.c
dwpSocket.c
EADME.txt
|
| de75089fb7216d19e9c22cce4dc62a49513477d3 |
09-Jun-2010 |
Carl Shapiro <cshapiro@google.com> |
Remove trailing whitespace.
Change-Id: I95534bb2b88eaf48f2329282041118cd034c812b
dwpAdb.c
dwpEvent.c
dwpMain.c
|
| e3c01dac83e6eea7f82fe81ed89cfbdd9791dbc9 |
21-May-2010 |
Carl Shapiro <cshapiro@google.com> |
Remove unused labels, variables, and functions. Enable warnings.
Change-Id: Icbe24eaf1ad499f28b68b6a5f05368271a0a7e86
dwpEvent.c
dwpHandler.c
dwpMain.c
dwpSocket.c
|
| d8cc332cff48fff1fc572617e9486afb2be4521a |
25-Feb-2010 |
Andy McFadden <fadden@android.com> |
Rearrange JDWP cleanup.
This moves the "get rid of the breakpoints" part before the "tell the
rest of the VM that there's no debugger attached" part. Hitting a
breakpoint when there's no debugger attached is not expected.
For bug 2461667.
dwpMain.c
|
| 43eb5015ca8bc0c859100b659d9c12934011a42e |
02-Feb-2010 |
Andy McFadden <fadden@android.com> |
Reduce VM shutdown verbosity.
Adds -verbose:shutdown flag, defaulted to "false". Cuts out most of the
log noise associated with shell commands.
dwpAdb.c
dwpMain.c
|
| 0171812e59e2520a4345b9bbadd4f7afa0a1de16 |
23-Jan-2010 |
Andy McFadden <fadden@android.com> |
Add streaming method profiling support.
The goal is to allow DDMS to start/stop method profiling in apps that
don't have permission to write to /sdcard. Instead of writing the
profiling data to disk and then pulling it off, we just blast the whole
thing straight from memory.
This includes:
- New method tracing start call (startMethodTracingDdms).
- Rearrangement of existing VMDebug method tracing calls for sanity.
- Addition of "vector" chunk send function, with corresponding
update to the JDWP transport function.
- Reshuffled the method trace start interlock, which seemed racy.
- Post new method-trace-profiling-streaming feature to DDMS.
Also:
- Added an internal exception-throw function that allows a printf
format string, so we can put useful detail into exception messages.
For bug 2160407.
dwp.h
dwpAdb.c
dwpEvent.c
dwpPriv.h
dwpSocket.c
|
| 5442d46fe1d0645d786a289c1143e830a6699b14 |
18-Dec-2009 |
Andy McFadden <fadden@android.com> |
Use writev() for DDMS packets.
The code was using the JDWP "expanding buffer" stuff, which is fine for
4-byte status messages but will be terrible for buffers of tracing and
profiling data. Now we construct the header in a separate buffer.
dwpAdb.c
dwpEvent.c
dwpPriv.h
dwpSocket.c
|
| c6e64ea32a7732e98975e37c5f8545c652a41ac8 |
05-Dec-2009 |
Andy McFadden <fadden@android.com> |
Don't assume debugger wants all exceptions.
The JDWP implementation in the VM keeps a list of the objects that the
debugger knows about, and prevents the GC from collecting them (which
isn't strictly necessary, but it's a whole lot easier than doing it
right). Because of the way it's implemented, it actually ended up
keeping track of all thrown exceptions, even if the debugger wasn't
interested in hearing about them.
With this change we now do a "late" registration of the exception
object, preventing exception-happy code from filling memory when the
debugger is attached.
dwpEvent.c
|
| 9ef546e0cad0b2cb22a522b7f3dde1994770d9ca |
14-Oct-2009 |
Andy McFadden <fadden@android.com> |
Bump "public" version from 1.1.0 to 1.2.0.
Also, send correct version in JDWP VirtualMachine.Version packet.
dwpHandler.c
|
| 6ff3c8fde9623dadad726dbd5e1658585c321751 |
13-Oct-2009 |
Andy McFadden <fadden@android.com> |
Add JDWP ReferenceType.ClassObject handler.
For bug 2157236.
dwpHandler.c
|
| f50c6d57afb09f8ed9da179a8bc8b409279ef8a6 |
03-Oct-2009 |
Andy McFadden <fadden@android.com> |
Add implementation of JDWP ClassType.NewInstance
Add a handler for the ClassType.NewInstance request, and some bits of
plumbing to go with it.
For bug 2157236.
dwpHandler.c
|
| 6196d15e42f317a8075f0d8b8c92b0c69736d037 |
04-Jun-2009 |
Andy McFadden <fadden@android.com> |
Retry on all ADB failures.
Change 2644 added retries when ADB went away. The VM occasionally
thinks it has reconnected to adbd as it's dying, which caused a
different type of failure, and the JDWP thread went off to sulk.
This rearranges the failure handling some more, so that all failures
are treated equally (with slight differences in logging).
dwpAdb.c
|
| 201a6b569b3820047bfe6dc22b793e646dd7eec2 |
02-Jun-2009 |
Andy McFadden <fadden@android.com> |
Added an explicit "shutting down" flag.
Change 2644 made the JdwpAdb stuff retry when the remote side went away.
Unfortunately this also made it retry when the VM wanted to shut down.
Since the JDWP thread is a non-daemon thread, this causes the VM to
stall forever.
This adds an explict flag to allow us to drop out of the retry loop.
dwpAdb.c
|
| 305efe65f9083b88562ce823bde6df027a2ff71e |
28-May-2009 |
Andy McFadden <fadden@android.com> |
Prevent JDWP thread death when adbd dies.
The handling for "remote side disconnected" was getting folded in with
more severe failures. This separates the two, returning to the connection
retry loop when adbd disappears.
One side-effect is that the JDWP thread will now wake up every couple of
seconds when adbd isn't running. Only affects "debuggable" apps.
This also reduces the priority on a couple of log messages.
For internal bug 1844156.
dwpAdb.c
|
| f6c387128427e121477c1b32ad35cdcaa5101ba3 |
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
xpandBuf.c
xpandBuf.h
dwp.h
dwpAdb.c
dwpConstants.c
dwpConstants.h
dwpEvent.c
dwpEvent.h
dwpHandler.c
dwpHandler.h
dwpMain.c
dwpPriv.h
dwpSocket.c
EADME.txt
|
| f72d5de56a522ac3be03873bdde26f23a5eeeb3c |
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
xpandBuf.c
xpandBuf.h
dwp.h
dwpAdb.c
dwpConstants.c
dwpConstants.h
dwpEvent.c
dwpEvent.h
dwpHandler.c
dwpHandler.h
dwpMain.c
dwpPriv.h
dwpSocket.c
EADME.txt
|
| 077f9d75d9701778830742b9c2afad4742635b58 |
19-Feb-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake/...@132276
dwpHandler.c
|
| 89c1feb0a69a7707b271086e749975b3f7acacf7 |
18-Dec-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Code drop from //branches/cupcake/...@124589
dwpAdb.c
|
| 2ad60cfc28e14ee8f0bb038720836a4696c478ad |
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
xpandBuf.c
xpandBuf.h
dwp.h
dwpAdb.c
dwpConstants.c
dwpConstants.h
dwpEvent.c
dwpEvent.h
dwpHandler.c
dwpHandler.h
dwpMain.c
dwpPriv.h
dwpSocket.c
EADME.txt
|