Mercurial > hg > truffle
view agent/src/share/classes/sun/jvm/hotspot/debugger/remote/RemoteDebugger.java @ 210:05712c37c828
6676016: ParallelOldGC leaks memory
Summary: ensure that GCTask threads release resource and handle memory
Reviewed-by: jmasa, chrisphi
author | jcoomes |
---|---|
date | Wed, 18 Jun 2008 18:36:47 -0700 |
parents | ba764ed4b6f2 |
children | d1605aabd0a1 |
line wrap: on
line source
/* * Copyright 2002 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 * 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 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. * */ package sun.jvm.hotspot.debugger.remote; import java.rmi.*; import sun.jvm.hotspot.debugger.*; /** <P> This interface describes the methods which are used in a remote debugging scenario. It is only necessary because RMI requires that all such methods throw RemoteException, which is a checked (i.e., not a Runtime) exception. Since we already have a suitable runtime exception (DebuggerException) present in the signatures for all of the debugger-related methods, we would like to repurpose this to wrap RemoteExceptions. This is done by wrapping the actual remote debugger object </P> <P> NOTE that this interface currently assumes that the debugger on the remote machine has already been attached to the target process or has opened the desired core file. This implies that the machine hosting the user interface can not effect attaching/detaching. Currently this restriction has been enforced to make the user interface less confusing, but there will also be security concerns with allowing clients to attach to arbitrary remote processes. </P> */ public interface RemoteDebugger extends Remote { public String getOS() throws RemoteException; public String getCPU() throws RemoteException; public MachineDescription getMachineDescription() throws RemoteException; public long lookupInProcess(String objectName, String symbol) throws RemoteException; public ReadResult readBytesFromProcess(long address, long numBytes) throws RemoteException; public boolean hasConsole() throws RemoteException; public String getConsolePrompt() throws RemoteException; public String consoleExecuteCommand(String cmd) throws RemoteException; public long getJBooleanSize() throws RemoteException; public long getJByteSize() throws RemoteException; public long getJCharSize() throws RemoteException; public long getJDoubleSize() throws RemoteException; public long getJFloatSize() throws RemoteException; public long getJIntSize() throws RemoteException; public long getJLongSize() throws RemoteException; public long getJShortSize() throws RemoteException; public long getHeapBase() throws RemoteException; public long getHeapOopSize() throws RemoteException; public long getLogMinObjAlignmentInBytes() throws RemoteException; public boolean areThreadsEqual(long addrOrId1, boolean isAddress1, long addrOrId2, boolean isAddress2) throws RemoteException; public int getThreadHashCode(long addrOrId, boolean isAddress) throws RemoteException; public long[] getThreadIntegerRegisterSet(long addrOrId, boolean isAddress) throws RemoteException; }