blob: f1fbe68ca1361a5505d38906a9039f0b47036579 [file] [log] [blame]
Raymond Gallardo2749cde2013-11-25 20:19:02 -08001'\" t
Michael Fang9a7441f2015-07-27 16:49:10 -07002.\" Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved.
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.\"
19.\" Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
20.\" or visit www.oracle.com if you need additional information or have any
21.\" questions.
22.\"
Raymond Gallardo2749cde2013-11-25 20:19:02 -080023.\" Arch: generic
24.\" Software: JDK 8
25.\" Date: 21 November 2013
26.\" SectDesc: Troubleshooting Tools
27.\" Title: jsadebugd.1
28.\"
29.if n .pl 99999
30.TH jsadebugd 1 "21 November 2013" "JDK 8" "Troubleshooting Tools"
Michael Fang9a7441f2015-07-27 16:49:10 -070031.\" -----------------------------------------------------------------
32.\" * Define some portability stuff
33.\" -----------------------------------------------------------------
34.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
35.\" http://bugs.debian.org/507673
36.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
37.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
38.ie \n(.g .ds Aq \(aq
39.el .ds Aq '
40.\" -----------------------------------------------------------------
41.\" * set default formatting
42.\" -----------------------------------------------------------------
43.\" disable hyphenation
44.nh
45.\" disable justification (adjust text to left margin only)
46.ad l
47.\" -----------------------------------------------------------------
48.\" * MAIN CONTENT STARTS HERE *
49.\" -----------------------------------------------------------------
J. Duke319a3b92007-12-01 00:00:00 +000050
Raymond Gallardo2749cde2013-11-25 20:19:02 -080051.SH NAME
52jsadebugd \- Attaches to a Java process or core file and acts as a debug server\&. This command is experimental and unsupported\&.
53.SH SYNOPSIS
54.sp
55.nf
J. Duke319a3b92007-12-01 00:00:00 +000056
Raymond Gallardo2749cde2013-11-25 20:19:02 -080057\fBjsadebugd\fR \fIpid\fR [ \fIserver\-id\fR ]
58.fi
59.nf
Jacob T Royal221af5e2009-05-04 18:28:26 -070060
Raymond Gallardo2749cde2013-11-25 20:19:02 -080061\fBjsadebugd\fR \fIexecutable\fR \fIcore\fR [ \fIserver\-id\fR ]
62.fi
63.sp
64.TP
65\fIpid\fR
66The process ID of the process to which the debug server attaches\&. The process must be a Java process\&. To get a list of Java processes running on a machine, use the jps(1) command\&. At most one instance of the debug server can be attached to a single process\&.
67.TP
68\fIexecutable\fR
69The Java executable from which the core dump was produced\&.
70.TP
71\fIcore\fR
72The core file to which the debug server should attach\&.
73.TP
74\fIserver-id\fR
75An optional unique ID that is needed when multiple debug servers are started on the same machine\&. This ID must be used by remote clients to identify the particular debug server to which to attach\&. Within a single machine, this ID must be unique\&.
76.SH DESCRIPTION
77The \f3jsadebugd\fR command attaches to a Java process or core file and acts as a debug server\&. Remote clients such as \f3jstack\fR, \f3jmap\fR, and \f3jinfo\fR can attach to the server through Java Remote Method Invocation (RMI)\&. Before you start the \f3jsadebugd\fR command, start the RMI registry with the \f3rmiregistry\fR command as follows where \fI$JAVA_HOME\fR is the JDK installation directory:
78.sp
79.nf
80\f3rmiregistry \-J\-Xbootclasspath/p:$JAVA_HOME/lib/sajdi\&.jar\fP
81.fi
82.nf
83\f3\fP
84.fi
85.sp
86If the RMI registry was not started, then the \f3jsadebugd\fR command starts an RMI registry in a standard (1099) port internally\&. The debug server can be stopped by sending a \f3SIGINT\fR to it\&. To send a SIGINT press \fICtrl+C\fR\&.
87.PP
88\fINote:\fR This utility is unsupported and may or may not be available in future releases of the JDK\&. In Windows Systems where \f3dbgeng\&.dll\fR is not present, Debugging Tools For Windows must be installed to have these tools working\&. The \f3PATH\fR environment variable should contain the location of jvm\&.dll used by the target process or the location from which the crash dump file was produced\&. For example, \f3s\fR\f3et PATH=%JDK_HOME%\ejre\ebin\eclient;%PATH%\fR\&.
89.SH SEE\ ALSO
90.TP 0.2i
91\(bu
92jinfo(1)
93.TP 0.2i
94\(bu
95jmap(1)
96.TP 0.2i
97\(bu
98jps(1)
99.TP 0.2i
100\(bu
101jstack(1)
102.TP 0.2i
103\(bu
104rmiregistry(1)
Michael Fang9a7441f2015-07-27 16:49:10 -0700105.RE
106.br
107'pl 8.5i
108'bp