Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I strongly recommend this tutorial on debugging in general.</p> <p><a href="http://www.vogella.com/articles/EclipseDebugging/article.html" rel="nofollow">http://www.vogella.com/articles/EclipseDebugging/article.html</a></p> <p>It takes you through all the features Eclipse offers in that department and is well worth the time.</p> <p>As far as the particular trick that might've helped, it might have been useful to set a breakpoint (i.e., clicking in the left margin of the code to make one of those blue pins appear). Then, when running in debug, you could stop <em>near</em> where the problem occurred, and step forward, beat by beat, using the "step into," "step forward," and "step return" commands at the top of debug window. While you're stepping around the code in that way, you might have the variables window open, so you could see what things are set in a manner they should be, etc. </p> <p>Alternatively, you could set a breakpoint on RuntimeException (even one that's caught), by clicking on the Breakpoints window in debug, and then licking the "J!" button (the mouseover text shows "add Java Exception Breakpoint."</p> <p>The debug view lets you do other cool stuff too, like:</p> <ul> <li>letting you set "watchpoints", so you can see when the application changes relevant fields, etc. </li> <li>"Drop to frame" so you can start your app in the middle. </li> <li>Set up step filters, so that "stepping" through I mentioned earlier can be done more efficiently. </li> <li>Create a detail formatter, a little snippet of java code that formats the output of a field so you can view it more cleanly in the debugger.</li> <li>And much more!</li> </ul> <p>Again, I recommend the above-referenced tutorial. And welcome to the wonderful world of debugging.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload