04-23-2010 07:42 PM
I recall reading someone else having this issue at one time, but, I can't seem to find that post.
I am having an issue trying to debug my application on a device (Storm 2). I get the debugger running and I can step through the code running on the device, but, all of the variables show up as null. Obviously, this makes it a bit difficult to debug .
Could some kind soul point me in the right direction to view the actual value of these variables? Heck, I'll even take pointers from a mean soul at this point...
IDE: Eclipse plug-in v220.127.116.11003212304-12 (18.104.22.168)
Device: Storm 2 - 9550 v22.214.171.1247 (Platform 126.96.36.1995)
04-23-2010 08:06 PM
I have more luck with System.out.printlin() when it comes to on-device debugging.
You can attach to the device single-step with the debugger, and view your variables in the output window.
04-23-2010 08:09 PM
I think the post you were thinking of was resolved because the data was not being returned. The poster thought that this was a bug in the OS, but he had missed the lack of response, and the debugger was not being helpful with him finding it.
When the variable show up as null, you mean they actually say null, or the debugger is telling you it doesn't understand them>
Does this apply to your objects, or RIM objects (like Strings).
if so, the likely problem is that the debug files on Eclipse don't match those for the device, so the debugger can't interpret the objects correctly.
I must admit, I don't know how t resolve this problem, but can you confirm this is actually what your problem is?
04-23-2010 08:54 PM
I have a feeling that is what it is because I get the same issue. Plug the device into the computer, debugger says debug files don't match, everything says that it is null.
10-26-2010 02:03 PM
Is there any known resolution for this? I am trying to debug using the Eclipse Plug In Mac beta and all of the variables show up as null, though I get no other error messages.
10-26-2010 02:10 PM
To tell you the truth, I don't recall. It could have been objects out of sync like Peter suggested. I would have thought that I would have marked this thread as solved, though. But, quite frankly, I barely remember this problem. Sorry, I wish I had a better answer.
11-11-2011 09:21 AM
Do you have the matching debug files? If not, then the debugger does not know how to handle the Objects.
I've also got very squiffy results sometimes when the code I had in the Development Environment had been updated, so was not the same as that on the device. Perhaps you could do a Build, sign and put it on the device and see if that helps anything?