Java Debugger/en - Versionsgeschichte

Mawalch am 11. Januar 2018 um 22:26 Uhr

2018-01-11T22:26:09Z

← Nächstältere Version		Version vom 11. Januar 2018, 22:26 Uhr
Zeile 54:		Zeile 54:
	an implicit exception handler for type [http://docs.oracle.com/javase/7/docs/api/java/lang/Throwable.html java.lang.Throwable].		an implicit exception handler for type [http://docs.oracle.com/javase/7/docs/api/java/lang/Throwable.html java.lang.Throwable].

	* For ''uncaught exception'' - the breakpoin will hit only if an exception is thrown but it is not handled by any handler, i.e., it is unhandled.		* For ''uncaught exception'' - the breakpoin will hit only if an exception is thrown but it is not handled by any handler, i.e., it is unhandled.

	'''Warning''': The JVM cannot always reliably tell whether a given exception is actually caught or uncaught. For details, refer to [http://docs.oracle.com/javase/7/docs/jdk/api/jpda/jdi/com/sun/jdi/event/ExceptionEvent.html#catchLocation() JDI documentation]		'''Warning''': The JVM cannot always reliably tell whether a given exception is actually caught or uncaught. For details, refer to [http://docs.oracle.com/javase/7/docs/jdk/api/jpda/jdi/com/sun/jdi/event/ExceptionEvent.html#catchLocation() JDI documentation]

Mawalch am 11. Januar 2018 um 22:16 Uhr

2018-01-11T22:16:34Z

Jv am 7. November 2014 um 14:19 Uhr

2014-11-07T14:19:46Z

@@ Zeile 61: / Zeile 61: @@
 [[Datei:expecco_JDebugger_002.png|right|thumb|JDebugger plugin: Java object inspector]]
@@ Zeile 77: / Zeile 79: @@
 For more information about default workspace and how to add classes and
 sources to it, please refer [[Java Browser/en|Java Browser plugin documentation]]

Jv: /* Breakpoints */

2014-10-09T11:03:20Z

Breakpoints

@@ Zeile 34: / Zeile 34: @@
 # ''Line Breakpoints'' - a traditional breakpoint set on particular line in particular method.
-# ''Exception Breakpoints'' - a breakpoint that suspends execution when an exception of specified type is thrown. This is useful to find out where a particular exception is thrown.
+# ''Exception Breakpoints'' - a breakpoint that suspends execution when an exception of specified type is thrown.
 == Object Inspector ==

Jv am 8. Oktober 2014 um 15:03 Uhr

2014-10-08T15:03:37Z

← Nächstältere Version		Version vom 8. Oktober 2014, 15:03 Uhr
Zeile 37:		Zeile 37:

	== Object Inspector ==		== Object Inspector ==

			[[Datei:expecco_JDebugger_002.png\|right\|thumb\|JDebugger plugin: Java object inspector]]

Jv am 8. Oktober 2014 um 14:51 Uhr

2014-10-08T14:51:33Z

@@ Zeile 4: / Zeile 4: @@
 The plugin provides a way to place [[#Breakpoints|breakpoints]] into a Java or Groovy code. When breakpoint hits (particular location in the code is reached), the program is stopped and [[#Debugger|a visual debugger]] appear. The debugger then can be used to inspect the state of the execution and/or single-step through the code.
 == Debugger ==
@@ Zeile 35: / Zeile 28: @@
 * ''Next'' - aka ''Step-into''. Single-step to next line in currently selected method or into a called method.
 * ''Out'' - aka ''Step-out''. Run until currently selected method returns and stop's at the method's caller.
 == Object Inspector ==

Jv am 8. Oktober 2014 um 14:50 Uhr

2014-10-08T14:50:15Z

← Nächstältere Version		Version vom 8. Oktober 2014, 14:50 Uhr
Zeile 1:		Zeile 1:
			== Introduction ==

	The ''Java Debugger plugin'' provides basic Java debugging facility. It allows for debugging of Groovy blocks and any other Java code run in remote JVM directly within expecco.		The ''Java Debugger plugin'' provides basic Java debugging facility. It allows for debugging of Groovy blocks and any other Java code run in remote JVM directly within expecco.

			The plugin provides a way to place [[#Breakpoints\|breakpoints]] into a Java or Groovy code. When breakpoint hits (particular location in the code is reached), the program is stopped and [[#Debugger\|a visual debugger]] appear. The debugger then can be used to inspect the state of the execution and/or single-step through the code.

	== Breakpoints ==		== Breakpoints ==

Jv: /* Breakpoints */

2014-10-08T14:45:11Z

Breakpoints

← Nächstältere Version		Version vom 8. Oktober 2014, 14:45 Uhr
Zeile 1:		Zeile 1:
	The ''Java Debugger plugin'' provides basic Java debugging facility. It allows for debugging of Groovy blocks and any other Java code run in remote JVM directly within expecco.		The ''Java Debugger plugin'' provides basic Java debugging facility. It allows for debugging of Groovy blocks and any other Java code run in remote JVM directly within expecco.

	== Breakpoints ==		== Breakpoints ==

			''Java Debugger'' plugin supports two kinds of breakpoints:

			# ''Line Breakpoints'' - a traditional breakpoint set on particular line in particular method.
			# ''Exception Breakpoints'' - a breakpoint that suspends execution when an exception of specified type is thrown. This is useful to find out where a particular exception is thrown.

	== Debugger ==		== Debugger ==

Jv: /* Managing Sources */

2014-10-08T11:39:13Z

Managing Sources

← Nächstältere Version		Version vom 8. Oktober 2014, 11:39 Uhr
Zeile 31:		Zeile 31:

	== Managing Sources ==		== Managing Sources ==

			''Java Debugger plugin'' uses [[Java Browser/en]] fro accessing
			source code. The source code for particular class / method is looked
			up in Java Browser's ''default workspace''. This means that if the default workspace does not contain a source code for the class, Java debugger will not show source code. However, it is still possible to
			inspect parameters and other local variables and even single-step.

			If the sources does not match the sources which the Java code
			has been compiled from, Java debugger may show invalid source code
			or line numbers may not match. There is no way to validate the sources
			matches the code loaded in remote JVM.

			For more information about default workspace and how to add classes and
			sources to it, please refer [[Java Browser/en\|Java Browser plugin documentation]]

Jv: /* Debugger */

2014-10-08T11:07:50Z

Debugger

← Nächstältere Version		Version vom 8. Oktober 2014, 11:07 Uhr
Zeile 16:		Zeile 16:
	<span style="color: red; padding: 3px; border: 2px solid red; border-radius:50%; background-color: #BBBBF6;">4</span> ''Method parameters and locals inspector'' - an embedded inspector showing all method parameters and local variables which are visible at current scope.		<span style="color: red; padding: 3px; border: 2px solid red; border-radius:50%; background-color: #BBBBF6;">4</span> ''Method parameters and locals inspector'' - an embedded inspector showing all method parameters and local variables which are visible at current scope.

	<span style="color: red; padding: 3px; border: 2px solid red; border-radius:50%; background-color: #BBBBF6;">5</span> ''Thread List'' - list showing all threads in the remote JVM. The ''Execution Stack'' pane shows execution stack of selected thread.		<span style="color: red; padding: 3px; border: 2px solid red; border-radius:50%; background-color: #BBBBF6;">5</span> ''Thread List'' - list showing all threads in the remote JVM. The ''Execution Stack'' pane shows execution stack of selected thread.

			Following debugging operations are available:

			* ''Continue'' - resumes execution until remote JVM terminates or another breakpoint is reached.
			* ''Abort'' - aborts execution of currently executing expecco Groovy block. If the selected thread does not execute a Groovy block abortion
			is not allowed.
			* ''Next'' - aka ''Step-over''. Single-step to next line in currently selected method. Does not enter into called methods.
			* ''Next'' - aka ''Step-into''. Single-step to next line in currently selected method or into a called method.
			* ''Out'' - aka ''Step-out''. Run until currently selected method returns and stop's at the method's caller.

	== Object Inspector ==		== Object Inspector ==

← Nächstältere Version		Version vom 11. Januar 2018, 22:16 Uhr
Zeile 1:		Zeile 1:
	== Introduction ==		== Introduction ==

	The ''Java Debugger plugin'' provides basic Java debugging facility. It allows for debugging of Groovy blocks and any other Java code run in remote JVM directly within expecco.		The ''Java Debugger plugin'' provides basic Java debugging facility. It allows for debugging of Groovy blocks and any other Java code run in remote JVM directly within expecco.

	The plugin provides a way to place [[#Breakpoints\|breakpoints]] into a Java or Groovy code. When breakpoint hits (particular location in the code is reached), the program is stopped and [[#Debugger\|a visual debugger]] appear. The debugger then can be used to inspect the state of the execution and/or single-step through the code.		The plugin provides a way to place [[#Breakpoints\|breakpoints]] into a Java or Groovy code. When breakpoint hits (particular location in the code is reached), the program is stopped and [[#Debugger\|a visual debugger]] appear. The debugger then can be used to inspect the state of the execution and/or single-step through the code.

	== Debugger ==		== Debugger ==
Zeile 10:		Zeile 10:
	The overall layout of Java debugger window is similar to debuggers for Smalltalk and JavaScript blocks. It consists of 5 panes:		The overall layout of Java debugger window is similar to debuggers for Smalltalk and JavaScript blocks. It consists of 5 panes:

	<span style="color: red; padding: 3px; border: 2px solid red; border-radius:50%; background-color: #BBBBF6;">1</span> ''Execution Stack'' - organized top-to-bottom, i.e., the currently executing method is the first entry in the list.		<span style="color: red; padding: 3px; border: 2px solid red; border-radius:50%; background-color: #BBBBF6;">1</span> ''Execution Stack'' - organized top-to-bottom, i.e., the currently executing method is the first entry in the list.

	<span style="color: red; padding: 3px; border: 2px solid red; border-radius:50%; background-color: #BBBBF6;">2</span> ''Source Code View'' - shows the source code of the currently selected method (in execution stack pane). Source for particular method may or may not be available. For details refer to section [[Managing Sources]]		<span style="color: red; padding: 3px; border: 2px solid red; border-radius:50%; background-color: #BBBBF6;">2</span> ''Source Code View'' - shows the source code of the currently selected method (in execution stack pane). Source for particular method may or may not be available. For details refer to section [[Managing Sources]]

	<span style="color: red; padding: 3px; border: 2px solid red; border-radius:50%; background-color: #BBBBF6;">3</span> ''this object inspector'' - an embedded inspector of '''this''' objects, i.e., on the receiver of the method.		<span style="color: red; padding: 3px; border: 2px solid red; border-radius:50%; background-color: #BBBBF6;">3</span> ''this object inspector'' - an embedded inspector of '''this''' objects, i.e., on the receiver of the method.

	<span style="color: red; padding: 3px; border: 2px solid red; border-radius:50%; background-color: #BBBBF6;">4</span> ''Method parameters and locals inspector'' - an embedded inspector showing all method parameters and local variables which are visible at current scope.		<span style="color: red; padding: 3px; border: 2px solid red; border-radius:50%; background-color: #BBBBF6;">4</span> ''Method parameters and locals inspector'' - an embedded inspector showing all method parameters and local variables which are visible at current scope.

	<span style="color: red; padding: 3px; border: 2px solid red; border-radius:50%; background-color: #BBBBF6;">5</span> ''Thread List'' - list showing all threads in the remote JVM. The ''Execution Stack'' pane shows execution stack of selected thread.		<span style="color: red; padding: 3px; border: 2px solid red; border-radius:50%; background-color: #BBBBF6;">5</span> ''Thread List'' - list showing all threads in the remote JVM. The ''Execution Stack'' pane shows execution stack of selected thread.

	Following debugging operations are available:		Following debugging operations are available:

	* ''Continue'' - resumes execution until remote JVM terminates or another breakpoint is reached.		* ''Continue'' - resumes execution until remote JVM terminates or another breakpoint is reached.
	* ''Abort'' - aborts execution of currently executing expecco Groovy block. If the selected thread does not execute a Groovy block abortion		* ''Abort'' - aborts execution of currently executing expecco Groovy block. If the selected thread does not execute a Groovy block abortion
	is not allowed.		is not allowed.
	* ''Next'' - aka ''Step-over''. Single-step to next line in currently selected method. Does not enter into called methods.		* ''Next'' - aka ''Step-over''. Single-step to next line in currently selected method. Does not enter into called methods.
	* ''Next'' - aka ''Step-into''. Single-step to next line in currently selected method or into a called method.		* ''Next'' - aka ''Step-into''. Single-step to next line in currently selected method or into a called method.
	* ''Out'' - aka ''Step-out''. Run until currently selected method returns and stop's at the method's caller.		* ''Out'' - aka ''Step-out''. Run until currently selected method returns and stop's at the method's caller.

Zeile 33:		Zeile 33:
	''Java Debugger'' plugin supports two kinds of breakpoints:		''Java Debugger'' plugin supports two kinds of breakpoints:

	# ''Line Breakpoints'' - a traditional breakpoint set on particular line in particular method.		# ''Line Breakpoints'' - a traditional breakpoint set on particular line in particular method.
	# ''Exception Breakpoints'' - a breakpoint that suspends execution when an exception of specified type is thrown.		# ''Exception Breakpoints'' - a breakpoint that suspends execution when an exception of specified type is thrown.

	=== Line Breakpoints ===		=== Line Breakpoints ===

	A line breakpoint could be placed to a [[ElementaryBlock_Element/en#Groovy_Blocks\|Groovy block]] or to any other Java code. When a line breakpoint is hit whole JVM is suspended, i.e., all running Java threads are suspended.		A line breakpoint could be placed to a [[ElementaryBlock_Element/en#Groovy_Blocks\|Groovy block]] or to any other Java code. When a line breakpoint is hit whole JVM is suspended, i.e., all running Java threads are suspended.

	To put a breakpoint in a Groovy block, just click in Groovy block editor left to the line number. The line breakpoint is indicated by a little red circle icon. To remove a breakpoint, just click on the breakpoint icon again.		To put a breakpoint in a Groovy block, just click in Groovy block editor left to the line number. The line breakpoint is indicated by a little red circle icon. To remove a breakpoint, just click on the breakpoint icon again.

	To put a breakpoint in any other Java code, open a Java browser window, navigate		To put a breakpoint in any other Java code, open a Java browser window, navigate
	to desired class and method and click left the line number.		to desired class and method and click left the line number.

	=== Exception Breakpoints ===		=== Exception Breakpoints ===

	An exception breakpoint hits when an exception of given type (or it's subtype) is thrown, i.e., at the point just before Java '''throw''' statement is executed. This is useful when an exception is thrown and possibly caught and re-thrown again to find out the original cause and debug there.		An exception breakpoint hits when an exception of given type (or it's subtype) is thrown, i.e., at the point just before Java '''throw''' statement is executed. This is useful when an exception is thrown and possibly caught and re-thrown again to find out the original cause and debug there.

	Exception breakpoints could be configured to trigger in two cases:		Exception breakpoints could be configured to trigger in two cases:
Zeile 69:		Zeile 69:
	''Java Debugger plugin'' uses [[Java Browser/en]] fro accessing		''Java Debugger plugin'' uses [[Java Browser/en]] fro accessing
	source code. The source code for particular class / method is looked		source code. The source code for particular class / method is looked
	up in Java Browser's ''default workspace''. This means that if the default workspace does not contain a source code for the class, Java debugger will not show source code. However, it is still possible to		up in Java Browser's ''default workspace''. This means that if the default workspace does not contain a source code for the class, Java debugger will not show source code. However, it is still possible to inspect parameters and other local variables and even single-step.
	inspect parameters and other local variables and even single-step.

	If the sources does not match the sources which the Java code		If the sources does not match the sources which the Java code
	has been compiled from, Java debugger may show invalid source code		has been compiled from, Java debugger may show invalid source code
	or line numbers may not match. There is no way to validate the sources		or line numbers may not match. There is no way to validate the sources
	matches the code loaded in remote JVM.		matches the code loaded in remote JVM.

	For more information about default workspace and how to add classes and		For more information about default workspace and how to add classes and
Zeile 85:		Zeile 84:
	The current version of JDebugger has some limitations:		The current version of JDebugger has some limitations:

	* A line breakpoint cannot be placed to a nested classes, i.e., to inner classes and to anonymous classes. Note, that UI event handlers, such as button click handlers, are usually implemented using anonymous classes.		* A line breakpoint cannot be placed to a nested classes, i.e., to inner classes and to anonymous classes. Note, that UI event handlers, such as button click handlers, are usually implemented using anonymous classes.
	* A breakpoint cannot be placed on a class which is loaded more than once in remote JVM.		* A breakpoint cannot be placed on a class which is loaded more than once in remote JVM.

	These limitations will be addressed in a future versions.		These limitations will be addressed in a future versions.