Hey, i'm trying to develop a program and i'm using the JDE.
everything was going fine until i run my program and receive an Uncaught exception thrown.
all the errors before i execute are easy to understand and read
but once i'm executing the Debugger and i get an exception thrown, i can't read any of that
it shows me Method called and lines where it was called but all that lead me to "source code is not available".
On the botton i have the name of each method called....but what metters is where is my mistake? and i can't find it, and also the debugger is not helping me at all...
can someone help me to read all this messages comming from the debugger so that maybe i can find a hint of where is my error...?
Your best tool for this is the call stack - keep backing down the call stack until you get to the call in *your* code that started the problem. If the call stack is not displayed in your JDE, enable it in "View / Call Stack"
but then when i look to the stacks, there are lots of method calls, and they make no sense after a while...it is not connected anymore
and the lines increase, but then start from a low number again, and increase...
but i still can't find where the Exception is comming from...
The only other suggestion would be to localize the issue by placing strategic breakpoints in the code, prior to the point where you think the exception is being thrown, and single-stepping the application until you trigger the exception.
yea i thought about that but what can i put in there to show me like "hey, i passed here..."?
cause when i use to do in other apps, i would simply do System.out.println();
i don't think a println would show anywhere..so what could i use instead?
Well it looks like you have errors with modules being loaded into the device more than once. To be more specific, you're trying to execute the ContactModel demo, and the class com.rim.samples.device.contactsdemo.ContactModel has more than one definition in the simulator. The exception is occurring on app launcher by the looks of it so it's reasonable that your app isn't even being executed, and therefore no code in your main function is being run. I would clean your simulator files and try launching it again.