diff options
| author | Sebastien Hertz <shertz@google.com> | 2014-08-12 09:09:37 +0200 |
|---|---|---|
| committer | Sebastien Hertz <shertz@google.com> | 2014-08-12 18:37:08 +0200 |
| commit | a22d115711b5158cfc67b4f260a5b40f3ab303ca (patch) | |
| tree | c44df9f9a0392fc5b8a7863be572db73cd8a6fa0 /test/008-exceptions/src/MultiDexBadInitWrapper1.java | |
| parent | 1c98286d8ceaf3715e06f50acd6f3b0aa5a06f2e (diff) | |
Fix crash in VirtualMachine.AllThreads JDWP command
When collecting all the started threads, we may encounter a thread in the
process of being started from Java code (Thread.start) in the threads list. The
crash occurs when we attempt to access the java.lang.Thread peer (calling
Thread::GetPeer) but the JNI global reference to it (Thread::jpeer) has not
been destroyed yet (which is verified with a check). This only happens when the
thread is starting up.
We now check the thread finished starting up before accessing the Java peer.
This also prevents from returning non-started threads in the reply.
Bug: 16660101
Change-Id: I9e445e5da3a6951143d6c3c9a0d4f136398fde2f
Diffstat (limited to 'test/008-exceptions/src/MultiDexBadInitWrapper1.java')
0 files changed, 0 insertions, 0 deletions