Java Development

[WorkHorse]

I have been given a project left off by another programmer to complete. However, upon opening the code and loading it on the simulator it produces a Null Exception Error 104. There is about 2000 lines of code and I don't know where to being debugging, or rather how to debug in this case. Is there a method in the eclipse plug in that would show me exactly where the error is coming from, or which line of code so that I may go from there? At this point I'm completely shooting in the dark. Again, thanks for any assistance. 

[simon_hain]

if it is a null pointer exception you can use "run, add exception breakpoint" to set a breakpoint on nullpointer exceptions.
do this only after the simulator started though, as the startup has its fair share of (controlled) nullpointers.

[WorkHorse]

Following your advice, I'm doing 

1.) right click on project  -> Run As -> Blackberry Simulator

     (simulator starts up, begins to load)

2.) I click on eclipse toolbar Run -> Add Java Exception Breakpoint

3.) Scroll through available options, add NullPointer Exception for 6.0.0, both checkboxes are checked which state "suspend on caught exceptions" and "suspend on uncaught exceptions"

The simulator loads up finally and I still get the error without knowing where in the code the error is supposedly coming from. Am I doing this correctly?

[simon_hain]

use "debug as", not "run as"

[WorkHorse]

A few things pop up, firstly a window stating The "net_rim_bis_client__ru.debug" file is missing. Please choose the missing file. At this point I don't click anything.

After a while a dialog box pops up 'Launching PROJECTNAME' has encountered a problem. Failed to connect to remote VM. Connection timed out. 

I click details and  it states: 

Failed to connect to remote VM. Connection timed out.
org.eclipse.jdi.TimeoutException

The simulator load bar is stuck at this point.

[simon_hain]

you can safely ignore the first message (press cancel or continue or whatever). if you don't the debugger cannot attach, thus resulting in the timeout message you get.

[WorkHorse]

But when I press cancel, just another missing debug file dialog box comes up. The name of the .debug that is missing is changed but there are a whole bunch of windows after I close the first one.

[simon_hain]

don't you have a "don't show this message again" option? i do.

[WorkHorse]

oh I do, I was wondering if the missing file dialogs generated would cause a problem, and if I select "don't show this again" if I needed the file name again I wouldn't know where to find it. If I try cancelling all the missing file dialogs rapidly (takes less than 10 seconds) at the end I get the following error:

The JRE thats listed in the program is 6.0.0 and I have these simulators:

[simon_hain]

click "don't ask me again" on all of them and continue...