Welcome!

Welcome to the Official BlackBerry Support Community Forums. This is your resource to discuss support topics with your peers, and learn from each other. New to the forum? Please visit the ‘Getting Started’ link below.
inside custom component

Java Development

Reply
Contributor
newton53
Posts: 40
Registered: ‎11-30-2011
My Carrier: Vodafone
Accepted Solution

Debugging - Step over, step into not working

OK, so the basics first -

 

Eclipse 4.2 epp ver 1.5.1.20121004-1506

BlackBerry Java Plug-in  ver 2.0.0.201207181003

 

Now the problem -

 

I set a breakpoint in my app, and the program suspends at the breakpoint. I press F6 to continue debugging, but instead of going to the next line, the program just continues on with execution, and one out of three times suspends at a completely random line. Also, the simulator still behaves as if the app as suspended at the first breakpoint. Any subsequent breakpoints after the first one have no effect; the control just passes through them. I have no idea what is causing this behaviour, I have changed literally nothing since the last time it was working. Anyone have any idea what's happening here?



I've got 99 problems and eclipse is all of them


Twitter

Please use plain text.
Developer
simon_hain
Posts: 13,783
Registered: ‎07-29-2008
My Carrier: O2 Germany

Re: Debugging - Step over, step into not working

ususally this means the code in the IDE and on the device are not in sync.
try to clean and re-deploy the project
----------------------------------------------------------
feel free to press the like button on the right side to thank the user that helped you.
please mark posts as solved if you found a solution.
@SimonHain on twitter
Please use plain text.
Contributor
newton53
Posts: 40
Registered: ‎11-30-2011
My Carrier: Vodafone

Re: Debugging - Step over, step into not working

haha wow, didn't expect it to be that of all things. thanks simon!

 

I'm clearly suffering from lack of caffeine. :Surrender:



I've got 99 problems and eclipse is all of them


Twitter

Please use plain text.