author | xgong |
Mon, 09 Sep 2019 11:19:51 +0800 | |
changeset 58042 | 95c206a3e53c |
parent 47216 | 71c04702a3d5 |
permissions | -rw-r--r-- |
1 | 1 |
# |
5547
f4b087cbb361
6941466: Oracle rebranding changes for Hotspot repositories
trims
parents:
1
diff
changeset
|
2 |
# Copyright (c) 2007, Oracle and/or its affiliates. All rights reserved. |
1 | 3 |
# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. |
4 |
# |
|
5 |
# This code is free software; you can redistribute it and/or modify it |
|
6 |
# under the terms of the GNU General Public License version 2 only, as |
|
7 |
# published by the Free Software Foundation. |
|
8 |
# |
|
9 |
# This code is distributed in the hope that it will be useful, but WITHOUT |
|
10 |
# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or |
|
11 |
# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License |
|
12 |
# version 2 for more details (a copy is included in the LICENSE file that |
|
13 |
# accompanied this code). |
|
14 |
# |
|
15 |
# You should have received a copy of the GNU General Public License version |
|
16 |
# 2 along with this work; if not, write to the Free Software Foundation, |
|
17 |
# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. |
|
18 |
# |
|
5547
f4b087cbb361
6941466: Oracle rebranding changes for Hotspot repositories
trims
parents:
1
diff
changeset
|
19 |
# Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA |
f4b087cbb361
6941466: Oracle rebranding changes for Hotspot repositories
trims
parents:
1
diff
changeset
|
20 |
# or visit www.oracle.com if you need additional information or have any |
f4b087cbb361
6941466: Oracle rebranding changes for Hotspot repositories
trims
parents:
1
diff
changeset
|
21 |
# questions. |
1 | 22 |
# |
23 |
# |
|
24 |
||
25 |
These scripts may be used to start SA debug server for SA/JDI |
|
26 |
purpose. The SADebugServerAttachingConnector will connect to |
|
27 |
SADebugServer. |
|
28 |
||
29 |
How to use? |
|
30 |
||
31 |
Before starting remote debug server, make sure that the environment |
|
32 |
variable JAVA_HOME points to the pathname of a J2SE 1.5. |
|
33 |
||
34 |
step 1: Start the rmiregistry server using one of the following |
|
35 |
commands as appropriate: |
|
36 |
||
37 |
start-rmiregistry.sh & |
|
38 |
start-rmiregistry64.sh & |
|
39 |
start-rmiregistry.bat |
|
40 |
||
41 |
step 2: For live process case, use one of the following commands |
|
42 |
as appropriate: |
|
43 |
||
44 |
start-debug-server.sh <pid of java process> |
|
45 |
start-debug-server64.sh <pid of 64 bit java process> |
|
46 |
start-debug-server.bat <pid of java process> |
|
47 |
||
48 |
For core file case, use one of the following commands as |
|
49 |
appropriate: |
|
50 |
||
51 |
start-debug-server.sh <path of java executable> <core file path> |
|
52 |
start-debug-server64.sh <path of java executable> <core file path> |
|
53 |
start-debug-server.bat <path of java executable> <core file path> |