Categories:
Audio (13)
Biotech (29)
Bytecode (36)
Database (77)
Framework (7)
Game (7)
General (507)
Graphics (53)
I/O (35)
IDE (2)
JAR Tools (101)
JavaBeans (21)
JDBC (121)
JDK (426)
JSP (20)
Logging (108)
Mail (58)
Messaging (8)
Network (84)
PDF (97)
Report (7)
Scripting (84)
Security (32)
Server (121)
Servlet (26)
SOAP (24)
Testing (54)
Web (15)
XML (309)
Collections:
Other Resources:
JDK 11 jdk.hotspot.agent.jmod - Hotspot Agent Module
JDK 11 jdk.hotspot.agent.jmod is the JMOD file for JDK 11 Hotspot Agent module.
JDK 11 Hotspot Agent module compiled class files are stored in \fyicenter\jdk-11.0.1\jmods\jdk.hotspot.agent.jmod.
JDK 11 Hotspot Agent module compiled class files are also linked and stored in the \fyicenter\jdk-11.0.1\lib\modules JImage file.
JDK 11 Hotspot Agent module source code files are stored in \fyicenter\jdk-11.0.1\lib\src.zip\jdk.hotspot.agent.
You can click and view the content of each source code file in the list below.
✍: FYIcenter
⏎ sun/jvm/hotspot/debugger/cdbg/ProcessControl.java
/* * Copyright (c) 2001, Oracle and/or its affiliates. All rights reserved. * ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. * * * * * * * * * * * * * * * * * * * */ package sun.jvm.hotspot.debugger.cdbg; import sun.jvm.hotspot.debugger.*; /** <P> A highly experimental interface for process control and debug events. May not be sufficiently portable; for this reason it has been factored out from the CDebugger interface and support for it is optional. </P> <P> The ProcessControl interface defines a process control and event model for debugging. When a process is attached to by the base Debugger, all threads in the target process are suspended. The ProcessControl interface allows resumption and re-suspension of the threads in the target process, setting of breakpoints, and reception of debugging events (breakpoint hit, signal received, etc.). </P> <P> Debugging events are generated one at a time by the target process. They must be queued up by the underlying debugging mechanism so that an attempt to send a second debugging event blocks until the first has been serviced with a call to debugEventResume. </P> */ public interface ProcessControl { /** Suspends all threads in the target process. A process is already suspended when attached to by {@link sun.jvm.hotspot.debugger.Debugger.attach(int)}. The application should check for the presence of a debug event via debugEventPoll() upon re-suspending the target process (if one is not yet known to be present.) @throw DebuggerException if the process is already suspended or if the suspension failed for some other reason. */ public void suspend() throws DebuggerException; /** Resumes all threads in the target process. @throw DebuggerException if the process is not suspended or if the resumption failed for some other reason. */ public void resume() throws DebuggerException; /** Indicates whether the target process is suspended. */ public boolean isSuspended() throws DebuggerException; /** Sets a breakpoint at the given address. The target process must be suspended in order to set a breakpoint. @throw DebuggerException if the breakpoint could not be set for some reason, including that a breakpoint is already set at that address or that the underlying debugging mechanism does not support that many breakpoints. */ public void setBreakpoint(Address addr) throws UnmappedAddressException, DebuggerException; /** Clears a breakpoint at the given address. The target process must be suspended in order to clear a breakpoint. @throw DebuggerException if the breakpoint could not be cleared for some reason, including that there was no breakpoint at that address. */ public void clearBreakpoint(Address addr) throws DebuggerException; /** Indicates whether a breakpoint is set at the given address. */ public boolean isBreakpointSet(Address addr) throws DebuggerException; /** Polls for the presence of a debug event. Does not wait for one to be generated; returns null if none was pending. The target process does not need to be suspended. Returns the same DebugEvent object until the debug event is handled via debugEventContinue. Typically the application will suspend the target process upon reception of a debug event but before handling it via a call to debugEventContinue. This ensures that the state of the thread which generated the debug event is precisely what it was when the event was generated. @return The pending debug event, or null if none pending. */ public DebugEvent debugEventPoll() throws DebuggerException; /** Informs the target process to resume past this debug event. The target process does not need to be suspended. Breakpoint debug events must be handled transparently by the implementation to re-execute the instruction and replace the breakpoint. (Ideally they should be replaced in such a way that there is no race condition between the re-execution and the re-insertion of the breakpoint.) All other kinds of exceptions or signals are passed on to the target process. @throw DebuggerException if no debug event is pending. */ public void debugEventContinue() throws DebuggerException; }
⏎ sun/jvm/hotspot/debugger/cdbg/ProcessControl.java
Or download all of them as a single archive file:
File name: jdk.hotspot.agent-11.0.1-src.zip File size: 1243786 bytes Release date: 2018-11-04 Download
⇒ JDK 11 jdk.httpserver.jmod - HTTP Server Module
2020-02-29, 145173👍, 0💬
Popular Posts:
What Is in Xerces-J-bin.2.12.2.zip? Xerces-J-bin.2.12.2.zip file is the distribution package ZIP fil...
JDK 17 jdk.localedata.jmod is the JMOD file for JDK 17 Localedata module. JDK 17 Locale Data module ...
Saxon-HE (home edition) is an open source product available under the Mozilla Public License. It pro...
What is ojdbc.jar - JDBC Driver for Oracle? ojdbc.jar is a JDBC driver from Oracle that provides dat...
Saxon-HE (home edition) is an open source product available under the Mozilla Public License. It pro...