/projects/netbeans-7.3/javacard.project/javahelp/org/netbeans/modules/javacard/project/docs/help/DebuggingApplications.html

https://gitlab.com/essere.lab.public/qualitas.class-corpus · HTML · 70 lines · 66 code · 4 blank · 0 comment · 0 complexity · 43b61c28e9b16ed21dc527d45ab53bfc MD5 · raw file 

    

  1. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    2. 

  2.  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    3. 

  3. <html lang="en-US"><head>
    4. 

  4. <!-- GenHTML revision 23224-->    <meta http-equiv="Content-type" content="text/html; charset=utf-8">
    5. 

  5. <link rel="StyleSheet" href="nbdocs://org.netbeans.modules.usersguide/org/netbeans/modules/usersguide/ide.css" type="text/css">
    6. 

  6.   <title>Debugging Applications - Java Card 3 Development
    7. 

  7.    </title></head><body class="body"><a name="DebuggingApplications"></a><h2>Debugging Applications</h2>
    8. 

  8. <p class="p">Debugging is the process of examining your application for errors. The process of debugging is accomplished by setting breakpoints and watches in your code and running it in the debugger. This enables you to execute your code one line at a time and examine the state of your application in order to discover any problems.</p>
    9. 

  9. <p class="p">The Java Debug Wire Protocol (JDWP) used by the IDE is heavy for
    10. 

  10. a small VM such as that provided by the Java Card RI. Consequently, the Java Card RI uses
    11. 

  11. KVM Debug Wire Protocol (KDWP) to provide a minimum set of debugging capabilities. The
    12. 

  12. debugproxy translates and sends the translated JDWP commands from the IDE to the Java Card RI
    13. 

  13. in KDWP format. Responses from the Java Card RI are converted into JDWP format by debugproxy
    14. 

  14. before it sends them to the IDE. </p>
    15. 

  15. <p class="p">The communication between the Java Card RI, debugproxy, and the IDE happens through sockets. Socket based communication enables developers to debug cjcre from remote hosts. For example, the Java Card RI could run on machine1, debugproxy could run on machine2, and the IDE could run
    16. 

  16. on machine3. Developers can also run the Java Card RI, debugproxy, and the IDE on same
    17. 

  17. host.</p><p class="p">Ports used by IDE communication to and from debugproxy and debugproxy communication to
    18. 

  18. and from the Java Card RI are distinguished by the names &#8220;listen port&#8221; and &#8220;remote
    19. 

  19. port&#8221; respectively.</p>
    20. 

  20. <p class="p">The Java Card platform debugger uses IDE menus and procedures for debugging applications. When you start a debugging session, the debugger windows appear automatically at the bottom of your screen. You can also debug applications that are running on a remote machine by attaching the debugger to the application process. See the appropriate Java Card 3 platform documentation on the Java Card 3 Kenai project site for detailed information about the Java Card 3 platform debugging protocol and procedures.</p>
    21. 

  21. 

  22. <p class="p">The following topics describe the basic sequence of activities completed by a developer
    23. 

  23. when debugging an application for the Java Card 3 platform:</p>
    24. 

  24. <table cellspacing="1" cellpadding="1" border="1">
    25. 

  25. <tr>
    26. 

  26. 	<td>Task</td>
    27. 

  27. 	<td>Use the IDE to:</td>
    28. 

  28. </tr>
    29. 

  29. <tr>
    30. 

  30. 	<td>Prepare to run the debugger</td>
    31. 

  31. 	<td><ul>
    32. 

  32. 	    	<li><a href="SettingBreakpoints.html">Set breakpoints in your code</a>:<br>
    33. 

  33. 			Debug &gt; New Breakpoint
    34. 

  34. 			</li>
    35. 

  35. 	    	<li><a href="SettingWatches.html">Set watches in your code</a>:<br>
    36. 

  36. 			Debug &gt; New Watch
    37. 

  37. 			</li>
    38. 

  38. </ul></td>
    39. 

  39. </tr>
    40. 

  40. <tr>
    41. 

  41. 	<td>Run the debugger</td>
    42. 

  42. 	<td><ul>
    43. 

  43. 	    	<li><a href="StartingDebugging.html">Start a debugger session</a>:<br>
    44. 

  44. 			Debug &gt; Debug Project<br>
    45. 

  45. 			Debug &gt; Debug File</li>
    46. 

  46. 	</ul></td>
    47. 

  47. </tr>
    48. 

  48. <tr>
    49. 

  49. 	<td>Monitor your code</td>
    50. 

  50. 	<td><ul>
    51. 

  51. 	<li><a href="SteppingThroughCode.html">Step through your code</a>:<br>
    52. 

  52. 	Debug &gt; Step <i>option</i></li>
    53. 

  53. 	<li>View debugging information.</li>
    54. 

  54. 	<li>View application threads.</li>
    55. 

  55. 	<li>Fix any errors and continue debugging.</li>
    56. 

  56. 	</ul></td>
    57. 

  57. </tr>
    58. 

  58. <tr>
    59. 

  59. 	<td>Finish the debugger session</td>
    60. 

  60. 	<td><ul>
    61. 

  61. 	    	<li>Stop the debugger:<br>
    62. 

  62. 			Debug &gt; Finish Debugger Session</li>
    63. 

  63. 			</ul></td>
    64. 

  64. </tr>
    65. 

  65. </table>
    66. 

  66. 

  67. 

  68. 

  69. </body>
    70. 

  70. </html>
    71.