--- a/jdk/src/solaris/doc/sun/man/man1/jsadebugd.1	Thu Apr 30 15:04:39 2009 -0700
+++ b/jdk/src/solaris/doc/sun/man/man1/jsadebugd.1	Mon May 04 18:28:26 2009 -0700
@@ -1,5 +1,4 @@
-.'" t
-." Copyright 2006 Sun Microsystems, Inc.  All Rights Reserved.
+." Copyright 2004 Sun Microsystems, Inc.  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
@@ -19,12 +18,12 @@
 ." Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa Clara,
 ." CA 95054 USA or visit www.sun.com if you need additional information or
 ." have any questions.
-." ` 
-.TH jsadebugd 1 "05 Aug 2006"
-." Generated by html2roff
+."
+.TH jsadebugd 1 "04 May 2009"
+." Generated from HTML by html2man (author: Eric Armstrong)
 
 .LP
-.SH NAME
+.SH "Name"
 jsadebugd \- Serviceability Agent Debug Daemon
 .LP
 .SH "SYNOPSIS"
@@ -45,30 +44,49 @@
 .LP
 
 .LP
+.RS 3
 .TP 3
 pid 
-process 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. 
+process 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(1) may be used. At most one instance of the debug server may be attached to a single process. 
+.RE
+
 .LP
+.RS 3
 .TP 3
 executable 
+.RE
+
 .LP
+.RS 3
 .TP 3
 Java executable from which the core dump was produced 
+.RE
+
 .LP
+.RS 3
 .TP 3
 core 
 Core file to which the debug server should attach. 
+.RE
+
 .LP
+.RS 3
 .TP 3
 server\-id 
 Optional 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. 
+.RE
+
 .LP
 .SH "DESCRIPTION"
 .LP
 
 .LP
 .LP
-\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:
+\f3jsadebugd\fP attaches to a Java process or core file and acts as a debug server. Remote clients such as jstack(1), jmap(1), and jinfo(1) can attach to the server using Java Remote Method Invocation (RMI). Before starting \f2jsadebugd\fP, 
+.na
+\f2rmiregistry\fP @
+.fi
+http://java.sun.com/javase/6/docs/technotes/tools/index.html#rmi must be started with:
 .LP
 .RS 3
 
@@ -87,26 +105,32 @@
 where \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.
 .LP
 .LP
-\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
+\f3NOTE \- This utility is unsupported and may or may not be available in future versions of the JDK. In Windows Systems where dbgeng.dll is not present, 'Debugging Tools For Windows' needs to be installed to have these tools working. Also, \fP\f4PATH\fP\f3 environment variable should contain the location of \fP\f4jvm.dll\fP\f3 used by the target process or the location from which the Crash Dump file was produced.\fP
+.LP
+.LP
+\f3For example, \fP\f4set PATH=<jdk>\\jre\\bin\\client;%PATH%\fP
 .LP
 .SH "SEE ALSO"
 .LP
 .RS 3
 .TP 2
-*
-jinfo 
+o
+jinfo(1) 
 .TP 2
-*
-jmap 
+o
+jmap(1) 
+.TP 2
+o
+jps(1) 
 .TP 2
-*
-jps 
+o
+jstack(1) 
 .TP 2
-*
-jstack 
-.TP 2
-*
-rmiregistry 
+o
+.na
+\f2rmiregistry\fP @
+.fi
+http://java.sun.com/javase/6/docs/technotes/tools/index.html#rmi 
 .RE
 
 .LP