[RFA/JVMTI] New JVMTI Environment Initialization/Allocation

[Keith Seitz]

Hi,

This patch rewrites the JVMTI allocation routine so that each JVMTI 
environment requested is allocated anew, since each environment will 
need (at the very least) a place to store event notification information 
(coming to a patch list near you soon).

I've also snuck in another little patch which adds another common test 
macro, this time for JVMTI_ERROR_ILLEGAL_ARGUMENT.

[Heaven help me if my linked list impl is off. I'm not used to not using 
JCL or STL anymore!]

I should mention that I have some tests written for all this new JVMTI 
work, but I need to figure out how to integrate this with existing 
framework. I'll either submit that if I figure it out or ask questions 
if I am defeated.

Keith

ChangeLog
2006-08-31  Keith Seitz  <keiths@redhat.com>

         * include/jvm.h (_Jv_JVMTI_Init): Declare.
         * jvmti.cc (_Jv_JVMTI_Init): New function.
         * prims.cc (_Jv_CreateJavaVM): Initialize JVMTI.

         * jvmti.cc (ILLEGAL_ARGUMENT): New macro.
         (_Jv_JVMTI_Allocate): Use ILLEGAL_ARUMENT.

         * jvmti.cc (_jvmtiEnvironments): New linked list of
         JVMTI environments.
         (FOREACH_ENVIRONMENT): New macro.
         (_envListLock): New object to act as synchronization lock
         for _jvmtiEnvironments.
         (_Jv_JVMTI_DisposeEnvironment): Check for NULL environment.
         Remove the environment from the list of known environments.
         (_Jv_GetJVMTIEnv): Add the new environment to the list
         of known environments.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jvmti-new-env.patch
Type: text/x-patch
Size: 3915 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/java-patches/attachments/20060901/7777f7da/attachment.bin>