0N/A." Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
0N/A." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
0N/A." This code is free software; you can redistribute it
and/or modify it
0N/A." under the terms of the GNU General Public License version 2 only, as
0N/A." published by the Free Software Foundation.
0N/A." This code is distributed in the hope that it will be useful, but WITHOUT
0N/A." ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
0N/A." FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
0N/A." version 2 for more details (a copy is included in the LICENSE file that
0N/A." accompanied this code).
0N/A." You should have received a copy of the GNU General Public License version
0N/A." 2 along with this work; if not, write to the Free Software Foundation,
0N/A." Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
0N/A." Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa Clara,
0N/A." CA 95054 USA or visit
www.sun.com if you need additional information or
0N/A." have any questions.
0N/A.TH jsadebugd 1 "05 Aug 2006"
0N/A." Generated by html2roff
0N/Ajsadebugd \- Serviceability Agent Debug Daemon
0N/A\fP\f3jsadebugd\fP pid [ server\-id ]
0N/A\f3jsadebugd\fP executable core [ server\-id ]
0N/Aprocess id of the process to which the debug server should attach. The process must be a Java process. To get a list of Java processes running on a machine, jps may be used. At most one instance of the debug server may be attached to a single process.
0N/AJava executable from which the core dump was produced
0N/ACore file to which the debug server should attach.
0N/AOptional unique id, needed if multiple debug servers are started on the same machine. This ID must be used by remote clients to identify the particular debug server to attach. Within a single machine, this ID must be unique.
0N/A\f3jsadebugd\fP attaches to a Java process or core file and acts as a debug server. Remote clients such as jstack, jmap, and jinfo can attach to the server using Java Remote Method Invocation (RMI). Before starting \f2jsadebugd\fP, rmiregistry must be started with:
0N/Awhere \f2$JAVA_HOME\fP is the JDK installation directory. If rmiregistry was not started, jsadebugd will start an rmiregistry in a standard (1099) port internally. Debug server may be stopped by sending SIGINT (pressing Ctrl\-C) to it.
0N/A\f3NOTE \- This utility is unsupported and may or may not be available in future versions of the JDK. jsadebugd is not currently available on Windows platforms.\fP