Uncaught Exceptions and the BlackBerry Whitescreen

Most BlackBerry developer experiences an uncaught excecption at some point.
Very oftens it's a RuntimeException the developer did not expect.


What's the best way to find it?

The default behaviour is to choose "continue" and search for the problem in the code.
This could be done by looking into the EventLog where uncaught exception will be logged with full stack trace (see also

But did you ever scroll through all the options?
There is "attach debugger" which is the easiest way to find the problem when this happens in the simulator.


Simply connect your Eclipse via "Debug As" -> "Remote Java application" to default port 8000. Afterwards(!) click "attach debugger" on the simulator.


Voilà! :)

You will be directly sent to the codeline where the exception occurs with full stack trace available, you can check all the variables. Finding an exception was never easier

Want to know more?

This week I tried a new Eclipse plugin to find unused code or code fragments with wrong visiblity (http://www.ucdetector.org/) and my project changed from 90 warnings (mostly deprecations) to 1300! But the problems view only shows me the first 100 of it (mostly the ones I already knew). Although I was used to Eclipse I couldn't find the setting for it, therefore this will be my 1st post here.

The settings is directly within the problems view, watch out for the small triangle on the right side:

and there it is:



And if your compiler stops after 100 warnings have a look here:

http://www.anujgakhar.com/2009/08/26/how-to-get-eclipse-to-show-more-than-100-errorswarnings/