dtrace support will not work after sharing is putback,
so there will be a need to make it working again.

For details, please, see Ken's email bellow:

Date: Mon, 22 Sep 2003 13:28:55 -0700

Subject: Re: sharing wrt dtrace



Fred's made the needed changes so the files compile but they won't work yet.
The bug ID under which we will be checking in the class data sharing code is

4416624: multiple JVM runtimes do not share memory between themselves

The sharing putback makes changes to several data structures but I think the
only relevant change for the dtrace code is that methodOops have been split
into two pieces, the read-write portion (still called methodOop) and the
read-only portion (called constMethodOop). The constMethodOop contains the
unchanging data including the bytecodes. The read-write methodOop points to
the constMethodOop and the frame points to the read-write methodOop. There is
a webrev of the current code at
http://analemma.sfbay/net/animorphic/export/kbr/webrevs/class_data_sharing/2/
though we're going to do some cleanup of the SCCS deltas before sending it
out for broader review in a day or so.

-Ken

  xxxxx@xxxxx   2003-09-22

N/A

  xxxxx@xxxxx   2003-11-03

New JvmOffsets constants have to be introduced/renamed and used consistently:
   methodOopDesc_constMethod
   constMethodOopDesc_flags
   constMethodOopDesc_code_size
   constMethodOopDesc_name_index
   constMethodOopDesc_signature_index
   constMethodOopDesc_has_linenumber_table

The fixes effect the following files in the dtrace directory:
   generateJvmOffsets.cpp, libjvm_db.c, jhelper.d

Some changes are already integrated as part of sharing support putback.
Others are still to be implemented.