agent/src/scripts/README

Mon, 28 Jul 2014 15:06:38 -0700

author
fzhinkin
date
Mon, 28 Jul 2014 15:06:38 -0700
changeset 6997
dbb05f6d93c4
parent 1907
c18cbe5936b8
child 6876
710a3c8b516e
permissions
-rw-r--r--

8051344: JVM crashed in Compile::start() during method parsing w/ UseRTMDeopt turned on
Summary: call rtm_deopt() only if there were no compilation bailouts before.
Reviewed-by: kvn

     1 #
     2 # Copyright (c) 2007, 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 #  
    23 #
    25 These scripts may be used to start SA debug server for SA/JDI
    26 purpose. The SADebugServerAttachingConnector will connect to
    27 SADebugServer.
    29 How to use?
    31 Before starting remote debug server, make sure that the environment
    32 variable JAVA_HOME points to the pathname of a J2SE 1.5.
    34 step 1: Start the rmiregistry server using one of the following
    35         commands as appropriate:
    37         start-rmiregistry.sh &
    38         start-rmiregistry64.sh &
    39         start-rmiregistry.bat 
    41 step 2: For live process case, use one of the following commands
    42         as appropriate:
    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>
    48         For core file case, use one of the following commands as
    49         appropriate:
    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>

mercurial