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