Thu, 27 May 2010 19:08:38 -0700
6941466: Oracle rebranding changes for Hotspot repositories
Summary: Change all the Sun copyrights to Oracle copyright
Reviewed-by: ohair
aoqi@0 | 1 | |
aoqi@0 | 2 | This dir contains a test for the JDI-SA implementation. |
aoqi@0 | 3 | |
aoqi@0 | 4 | sagtest.java, sagtarg.java are a normal JDI regression test |
aoqi@0 | 5 | that uses TargetAdapter.java, TargetListener.java, TestScaffold.java, |
aoqi@0 | 6 | and VMConnection.java. |
aoqi@0 | 7 | |
aoqi@0 | 8 | This test starts the debuggee, sagtarg.java, which just does a wait. |
aoqi@0 | 9 | The test then calls sagdoit.java which calls all the JDJI interface |
aoqi@0 | 10 | functions. Well, it doesn't call them all yet, but that is the plan. |
aoqi@0 | 11 | At least all that are interesting to the JDI-SA client. The result of |
aoqi@0 | 12 | each call is sent to stdout |
aoqi@0 | 13 | |
aoqi@0 | 14 | The script runjpda.sh runs this test. It then runs the targ part of |
aoqi@0 | 15 | the test and calls gcore on it to get a core dump into file sagcore. |
aoqi@0 | 16 | Do |
aoqi@0 | 17 | runjpda.sh >& kk |
aoqi@0 | 18 | |
aoqi@0 | 19 | to run this. |
aoqi@0 | 20 | |
aoqi@0 | 21 | NOTE that this produces 1000s of lines of output |
aoqi@0 | 22 | so be sure to redirect to a file. |
aoqi@0 | 23 | |
aoqi@0 | 24 | File sagclient.java is a test program that uses the JDI-SA |
aoqi@0 | 25 | client to connect to a core file or pid and then calls sagdoit |
aoqi@0 | 26 | which calls the JDI methods. |
aoqi@0 | 27 | |
aoqi@0 | 28 | The script runsa.sh can be used to run sagclient on sagcore: |
aoqi@0 | 29 | runsa.sh sagcore >& kk1 |
aoqi@0 | 30 | |
aoqi@0 | 31 | You can then look at the differences between the runjpda.sh |
aoqi@0 | 32 | and the runsa.sh run to see if there are bugs. Note that the |
aoqi@0 | 33 | order of things might be different. |
aoqi@0 | 34 | |
aoqi@0 | 35 | |
aoqi@0 | 36 | ----------------------------------------- |
aoqi@0 | 37 | |
aoqi@0 | 38 | runjdb.sh contains a script that will run jdb on a core file |
aoqi@0 | 39 | using the JDI-sa binding. |