###@###.### 2003-09-30

Official Solaris version to build HS and SDK is Solaris 8, but jhelper.d
has to be compiled (and maybe even linked with libjvm.so on Solaris 10.
It is because there is no Dtrace bellow Solaris 10.

For details, please, see email thread bellow:

> Date: Mon, 18 Aug 2003 00:18:17 -0700 (PDT)
> From: Serguei Spitsyn <###@###.###>
> Subject: Re: Development of pstack/dtrace support
> To: ###@###.###
> Cc: ###@###.###
>
> Hi Sundar!
>
> > Date: Mon, 18 Aug 2003 11:36:55 +0530
> > From: Athijegannathan Sundararajan <###@###.###>
> > Subject: Re: Development of pstack/dtrace support
> > To: Serguei Spitsyn <###@###.###>
> >
> > Hi Serguei,
> >
> > As I understand, we build jhelper.d only when we build jvm on Solaris
> > 10. This is unlikely. Release engg's official build platform for Tiger
> > is Solaris 8. Hence, I think we should:
> >
> > 1) precompile jhelper.d on a Solaris 10 machine and putback
> > the binary jhelper.o (along with source). We change makefile only to
> > link jhelper.o with libjvm.so.
>
> I'm not sure if it is a good way.
>
> (1-st), because jhelper.d depends on current JvmOffsets.h
> which depends on current libjvm.so structs layout.
> So, if layout (and so the generated JvmOffsets.h) is changed
> then jhelper.d has to be recompiled. But it can be recompiled on
> Solaris 10 only. So, we do not solve the problem in this way.
>
> (2-nd), because I saw that if jhelper.o is linked with libjvm.so
> on Solaris 8 then ustack helper does not working. I tried this ones.
> Maybe it'll be good if I verify it again to be completely sure.
> BTW, there was no problem to link libjvm.so on Solaris 10
> and use it on both Solaris 8 and 10.
> But of course, all *.o (except jhelper.o) were compiled on Solaris 8.
>
> We discussed this problem with Tom but didn't find a solution yet.
>
> Thanks,
> Serguei


> Date: Wed, 27 Aug 2003 14:46:36 +0530
> From: Athijegannathan Sundararajan <###@###.###>
> Subject: dtrace support
> To: ###@###.###
> Cc: ###@###.###, ###@###.###
>
> Hi,
>
> We have a release engineering problem with dtrace support.
>
> The pstack support can be built on Solaris 8. But dtrace support can be
> built only on Solaris 10. Currently, makefile checks for Solaris 10 and
> builds dtrace support. Because Tiger official build platform is Solaris
> 8, we won't build dtrace support at all.
>
> We thought of building Solaris 10 specific stuff on Solaris 10 and
> putback binary into the workspace. This has been discussed and found
> that this is not a good alternative. Serguei forwarded me some past
> communications in this regard. As of now, we do not have any solution
> for this problem.
>
> pstack support could still be useful, hence I think we can putback the
> changes (from Serguei's changes) as it is. We can attempt to solve
> dtrace build on Solaris 8 issue later. I am suggesting this so that we
> will putback the changes before late binding deadline. Is this okay? If
> so, we will proceed with putting back changes ASAP.
>
> Thanks,
> -Sundar

Thanks,
Serguei

###@###.### 2003-10-02

For details, please also refer to bugs:
  RFE: 4828776 Cat/Subcat: hotspot/other P3/S5
  Synopsis: Provide Java call stack support for dtrace

  Bug: 4915456 Cat/Subcat: java/build P3/S5
  Synopsis: need to copy pstack support binaries from hotspot build during j2se build

Some tests are placed in attachment.
To run, please, do the following:

0. rlogin on some Solaris-10 machine with Dtrace.
   You can use my machines:
        tomsk.sfbay: x86 machine with Solaris build d10_34 BFU'ed
        nsk.sfbay: sparc machine with Solaris build d10_34 BFU'ed

   Before tests run, please ask to add dtrace priviledges for you on these machines.
   Default priviledges has to be added into the file /etc/user_attr as follows:
ss45998@tomsk cat /etc/user_attr
...
#pragma ident "@(#)user_attr 1.5 01/12/11 SMI"
root::::auths=solaris.*,solaris.grant;profiles=All
lp::::profiles=Printer Management
adm::::profiles=Log Management
never::::defaultpriv=basic,dtrace_kernel,dtrace_proc,dtrace_user
ss45998::::defaultpriv=basic,dtrace_kernel,dtrace_proc,dtrace_user
sa120814::::defaultpriv=basic,dtrace_kernel,dtrace_proc,dtrace_user

1. cd $YOUR_WRK_DIR

2. Unpack tests.tar.gz.Z into $YOUR_WRK_DIR directory
   You will find new 'tests' directory created

3. % cd tests

4. Run tests with -jdk $YOUR_SDK option:
   % run dtst -jdk $YOUR_SDK

   Automated tests will be run. You will see some output similar
   to that contained in the file $YOUR_WRK_DIR/tests/x86.dtrace.out

   The tests are not auto-checked, so you have to verify wether output is correct or not.

5. To run tests with java_g you need to used 'dtstg' subcommand instead of 'dtst':
   % run dtstg -jdk $YOUR_SDK

6. It is possible to run separated test or/and pass a couple of flags to java:
   % run dtst2 -jdk $YOUR_SDK -server -Xcomp

Please, let me know if there are any questions.

Thanks,
Serguei