t
Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved.
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.

This code is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License version 2 only, as
published by the Free Software Foundation.

This code is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
version 2 for more details (a copy is included in the LICENSE file that
accompanied this code).

You should have received a copy of the GNU General Public License version
2 along with this work; if not, write to the Free Software Foundation,
Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.

Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
or visit www.oracle.com if you need additional information or have any
questions.

Arch: generic
Software: JDK 8
Date: 21 November 2013
SectDesc: Troubleshooting Tools
Title: jsadebugd.1

-----------------------------------------------------------------
* Define some portability stuff
-----------------------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
http://bugs.debian.org/507673
http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----------------------------------------------------------------
* set default formatting
-----------------------------------------------------------------
disable hyphenation
disable justification (adjust text to left margin only)
-----------------------------------------------------------------
* MAIN CONTENT STARTS HERE *
-----------------------------------------------------------------
jsadebugd - Attaches to a Java process or core file and acts as a debug server. This command is experimental and unsupported.

 

jsadebugd pid [ server-id ]

 

jsadebugd executable core [ server-id ]

pid The 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.

executable The Java executable from which the core dump was produced.

core The core file to which the debug server should attach.

server-id An 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.

The \f3jsadebugd command attaches to a Java process or core file and acts as a debug server. Remote clients such as \f3jstack, \f3jmap, and \f3jinfo can attach to the server through Java Remote Method Invocation (RMI). Before you start the \f3jsadebugd command, start the RMI registry with the \f3rmiregistry command as follows where $JAVA_HOME is the JDK installation directory:

 
\f3rmiregistry -J-Xbootclasspath/p:$JAVA_HOME/lib/sajdi.jar

 
\f3

If the RMI registry was not started, then the \f3jsadebugd command starts an RMI registry in a standard (1099) port internally. The debug server can be stopped by sending a \f3SIGINT to it. To send a SIGINT press Ctrl+C.

Note: This utility is unsupported and may or may not be available in future releases of the JDK. In Windows Systems where \f3dbgeng.dll is not present, Debugging Tools For Windows must be installed to have these tools working. The \f3PATH 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\f3et PATH=%JDK_HOME%\ejre\ebin\eclient;%PATH%.

0.2i jinfo(1)

0.2i jmap(1)

0.2i jps(1)

0.2i jstack(1)

0.2i rmiregistry(1)

'pl 8.5i 'bp