Bring across the JDWP implementation.
This compiles and links, but does nothing until we fill out the 100 or so
unimplemented methods in "debugger.cc". Note that I also need to add the
extra command-line handling for the JDWP agent stuff, and add calls from
the runtime to the various "something interesting is going on" hooks.
Change-Id: I477cf3caf9e248c384ce1d739cbfadb60e2008bc
diff --git a/src/thread.cc b/src/thread.cc
index 42d9f1a..1800834 100644
--- a/src/thread.cc
+++ b/src/thread.cc
@@ -26,6 +26,7 @@
#include <iostream>
#include <list>
+#include "debugger.h"
#include "class_linker.h"
#include "class_loader.h"
#include "context.h"
@@ -165,10 +166,7 @@
// in progress while we were starting up.)
runtime->GetThreadList()->WaitForGo();
- // TODO: say "hi" to the debugger.
- //if (gDvm.debuggerConnected) {
- // dvmDbgPostThreadStart(self);
- //}
+ Dbg::PostThreadStart(self);
// Invoke the 'run' method of our java.lang.Thread.
CHECK(self->peer_ != NULL);
@@ -767,10 +765,7 @@
// this.vmData = 0;
SetVmData(peer_, NULL);
- // TODO: say "bye" to the debugger.
- //if (gDvm.debuggerConnected) {
- // dvmDbgPostThreadDeath(self);
- //}
+ Dbg::PostThreadDeath(this);
// Thread.join() is implemented as an Object.wait() on the Thread.lock
// object. Signal anyone who is waiting.