This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: [RFA] Suspend counting for JDWP
- From: Keith Seitz <keiths at redhat dot com>
- To: Bryce McKinlay <mckinlay at redhat dot com>
- Cc: Java Patches <java-patches at gcc dot gnu dot org>
- Date: Thu, 06 Jul 2006 13:28:40 -0700
- Subject: Re: [RFA] Suspend counting for JDWP
- References: <44A044F6.1010208@redhat.com> <44A2A19E.9050201@redhat.com> <44A2B5E7.1090901@redhat.com> <44A32681.5000401@redhat.com>
Bryce McKinlay wrote:
Clearly, "jvmtiError SuspendThread(jvmtiEnv* env, jthread thread)" is
more-or-less equivalent to "_Jv_DebugSuspendThread(_Jv_Thread_t)".
Yep, they pretty much are.
Its your call. Certainly if you think JVMTI is going to hold up JDWP
work, I wouldn't want to see too much time spent on it. But, I think
that implementing the parts needed by JDWP shouldn't be a huge
undertaking, It should actually be helpful, by clearly defining the
interfaces through which JDWP should communicate with the VM, rather
than ending up with bits and pieces of JDWP support code scattered around.
I don't really have a definitive answer on that. By and large, I agree
with you. JVMTI has always been on the radar, but I've always been
hesitant to start jumping into another project without any intention of
finishing it for the foreseeable future.
Any way, I think I'll just see about setting something up to start JVMTI
stuff for this. With careful warnings about it being almost entirely
unimplemented, it shouldn't really hurt.
Keith