anchor.diff:  
   .  First, you set breakpoints and/or watches before the problematic lines of code where you suspect the bug.
   **  If you want to watch a variable's value: Right-click on a variable and select New Watch from the context menu.
  -**  If you want to step through the execution line by line: Right-click on a line and choose Toggle Line Breakpoint; a pink box appears as a mark.
  +**  If you want to step through the execution line by line: btn:[RMB] click on a line and choose "`Toggle Line Breakpoint`"; a pink box appears as a mark.
   
   .  Choose menu:Debug[Debug Main Project] to start a debugger session for the whole project. Or, btn:[RMB] click a file and select "`Debug File`" to debug only one file.
   .  The application starts running normally. If you have set a breakpoint, the execution stops in this line. Debugger windows open and print debugger output.
   .  You can do many things now to track down a bug:
   **  Inspect the values of local variables.
   **  Use the Step buttons in the top to step into, out of, and over expressions while you watch the execution.
  -**  Navigate through your application's call stack. Right-click on threads to suspend or resume them.
  +**  Navigate through your application's call stack. btn:[RMB] click on threads to suspend or resume them.
   **  Choose menu:Debug[Evaluate Expression] from the menu to evaluate an expression.
   **  Move the mouse pointer over a variable to inspect its value in a tooltip.
   **  Inspect the classes loaded on the heap and the percentage and number of object instances. btn:[RMB] click a class in the Loaded Classes window and choose Show in Instances view (JDK 6 only).
  
positive.code: 
  If you do not see a Profiler menu in the jMonkeyEngine SDK, you need to download the Profiler plugin first.
  
  .  Open the Tools &gt; Plugins menu, and got to the “Available plugins tab
  .  Find the “Java Profiler plugin (“Java SE category) and check the Install box.
  .  Click the install button and follow the instructions.
  .  When you start the profiler for the first time, you are prompted to run a calibration once. Click OK in the “Profiler integration dialog to complete the installation process.
  
  
  === Monitoring and Analyzing
  
negative.code: 
  Profiling points are similar to debugger breakpoints: You place them directly in the source code and they can trigger profiling behaviour when hit.
  
  *  Open a class in the browser, btn:[RMB] click in a line, and select menu:Profiling[Insert Profiling Point] to add a profiling point here.
  *  Use Profiling points if you need a trigger to reset profiling results, take a snapshot or heap dump, record the timestamp or execution time of a code fragment, stop and start a load generator script (requires the load generator plugin).
  *  Open the Profiling Points window to view, modify and delete the Profiling Points in your projects.
  
  