Be sure that what happened is really a bug.Search bugzilla for existing bugs like yours BEFORE you file it.

When filing bugs against the JDT or Platform Debug project, we ask that you use your better judgment, and most importantly common sense before filing a bug. For more information about contributing to JDT or Platform Debug in general, or for questions about its internals, contact or respectively. For more information on how to become a committer, check the standard Eclipse process (see New Committer Election). ANY serious developers or contributors will be enthusiastically welcomed. Platform and JDT debug are driven by a small development group with limited resources.

1 Contributing to JDT or Platform Debug.

This prevented the debugger from pausing program flow during a caught NullPointerException. In order to prevent this from happening, I: As a result, I constantly had to keep pressing the button to continue code execution.

I didn’t really need to know about this since the exception was being caught and handled, but eclipse would pause debugging every time this happened and tell me that the source wasn’t available. In my case, a null pointer exception was being thrown somewhere in Java’s Transformer.IsRuntimeCode(ProtectionDomain) function. I had this very annoying problem for a long time but was finally able to solve it. In general is there anyway to tell it that it doesn’t and just have it throw up an error dialog of some kind instead? Answer It seems that Eclipse seems to think it needs the source when an exception is thrown by the internal JUnit code. My main question is though, how can I tell Eclipse to skip this dialog when the source is not available and allow me to continue to debug my own code? I have the JUnit runtime jar so Why does Eclipse expect me to have all the referenced tools source code in order to debug my own code (seems somewhat silly)?

I know I should probably go and try and download the source from somewhere, but I really don’t want to because I have no interest in stepping into the JUnit code.

How to use eclipse debugger for junit