Running and debugging in JCIDE 6
Posted: Thu Jun 04, 2020 4:53 am
JCIDE allows you to debug Java card applet through the Debugger for Java Card. It's a lightweight Java Card debugger based on Java Debug Server, which extends the Language Support for Java by Red Hat, DebuggerServerProxy and Simulator support for Java Card by JavaCos.
Here's a list of supported debugging features:
Once you press F5, the debugger will start debugging. You can also start a debugging session from the Debug menu or the Run view opened by the Run icon in the Activity Bar on the side of JCIDE. Or from "Run or Debug Configuration" view to start a debuging session.
"/>
Threads and Call Stacks
You can see all the running threads in the Call Stack pane and work with individual thread using the context menu.
Expression evaluation
The debugger also lets you evaluate expressions in the WATCH window . You can also use this feature for conditional breakpoint setting.
Conditional breakpoint
With the help of expression evaluation, the debugger also supports conditional breakpoint. You can set your breakpoint to break when expression evaluates to true."/>
Logpoints
Logpoints is also supported by the Debugger. Logpoints allow you to send output to debug console without editing code. They're different from breakpoints because they don't stop the execution flow of your application."/>
Variables
Configuration
"/>
Here's a list of supported debugging features:
- Breakpoints
Continue
Step In/Out/Over
Variables
Call Stacks
Threads
Evaluation
Once you press F5, the debugger will start debugging. You can also start a debugging session from the Debug menu or the Run view opened by the Run icon in the Activity Bar on the side of JCIDE. Or from "Run or Debug Configuration" view to start a debuging session.
"/>You can see all the running threads in the Call Stack pane and work with individual thread using the context menu.
The debugger also lets you evaluate expressions in the WATCH window . You can also use this feature for conditional breakpoint setting.
With the help of expression evaluation, the debugger also supports conditional breakpoint. You can set your breakpoint to break when expression evaluates to true.
"/>Logpoints is also supported by the Debugger. Logpoints allow you to send output to debug console without editing code. They're different from breakpoints because they don't stop the execution flow of your application.
"/>"/>