Java Platform Debugger Architecture: Difference between revisions

Revision as of 23:44, 20 February 2020

Latest revision as of 07:20, 30 October 2024

(3 intermediate revisions by 3 users not shown)

Line 1:

{{Short description|APIs for Java programming language}}

The '''Java Platform Debugger Architecture''' (JPDA) is a collection of [[API]]s to [[debugging|debug]] [[Java (programming language)|Java]] code.

* Java Debugger Interface (JDI) -– defines a high-level Java language interface that developers can easily use to write remote debugger application tools.

* [[Java Virtual Machine Tools Interface]] (JVMTI), – a native interface that helps to inspect the state and to control the execution of applications running in the [[Java virtual machine|Java Virtual Machine]] ([[JVM]]).

* Java Virtual Machine Debug Interface (JVMDI)- – ''JVMDI was deprecated in J2SE 5.0 in favor of JVM TI, and was removed in Java SE 6.''

* [[Java Debug Wire Protocol]] (JDWP) -– defines communication between debuggee (a Java application) and [[debugger]] processes.

[[File:JPDA architecture.png|thumb|JPDA architecture]]

==Java Debugger Interface (JDI)==

JDI is the highest-layer of the Java Platform Debugger Architecture. It allows to access the [[Java virtual machine|JVM]] and the internal variables of the debugged program. It also allows to set [[Breakpointbreakpoint]]s, [[Steppingstepping (debugging)|stepping]], and handle threads.<ref>{{cite web

| url=https://www.baeldung.com/java-debug-interface

| title=An Intro to the Java Debug Interface (JDI)

Line 19 ⟶ 20:

* [[Eclipse (software)|Eclipse]], an open-source IDE integrated with JPDA support

* [[IntelliJ IDEA]], a commercial open-source Java IDE with integrated JPDA support

* [[JSwat]], an open-source Java debugger using the JPDA

* [[NetBeans]], an open-source IDE using the JPDA