09-21-2010 06:50 AM
thx to Mark Sohm and others helping and testing so much to find the reason why the Debugger doesnt work.
we failed - all looks good but the Debugger still won't connect to remote VM
so le last step was to create all from scratch:
* create new Parallels VM with Windows 7 64 bit
* install SDK 32 bit
* install Full Eclipse PlugIn and also classic Eclipse + Updatesite
* install new signature keys
and finally it works again
from my POV there's no difference to the prev. installation, but who knows
so I'll watch all my steps carefully - so perhaps if it happens again we'll find the reason
If you're interested: I have described all steps here:
12-07-2010 02:59 AM - edited 12-07-2010 03:01 AM
I have been using the eclipse plugin for blackberry (Galileo) since a while now..and everything seemed to work fine till a month back..suddenly my debugger started giving issues.It shows connection timed out exception and does not let the debugger attach at all.
Initially i used to do some steps like cleaning the simulator, creating a new debug configuration,re-installing the eclipse plugin, re-booting the system,etc and that used to work for 1-2 debug cycles.However off late, the debugger ALWAYS fails to attach and is really becoming a bottle-neck for me.
I went through the thread and the solution, but i am not able to completely understand how do i need to go about it.Can anyone please make it simpler and easily doable for me?I am a newbie and not at all known to the areas of the parallel VMs and jdk bits talked about in the solution.
Any help would be greatly appreciated,
12-16-2010 05:53 PM
I suspect this problem is created by the .NET framework eclipse is built on. I had the same problem when using Visual Studio 2002 to develop software. The problem was resolved when I upgraded to VS 2005.
In the meantime, if cleaning the simulator and the eclipse debugger doesn't work, I create a new project and transfer the source files to the new project. It's a pain but it works. BTW, I had to do the same thing when I used VS 2002.
12-16-2010 05:58 PM
Eclipse is built on top of Java, not .Net.
01-11-2011 02:32 PM
I have been having the same problem and something Mark mentioned led me to the solution.
My antivirus (Norton) was blocking the ports needed between the simulator and VM. I disabled the firewall settings in Norton and the debugger is working like new again.
Hope hope this helps if you also have antivirus installed.
01-11-2011 08:30 PM
That would make sense. From what I remeber the "connection timed out" exceptions were network time outs. Heck, even the PlayBook sim relies on new connections.
@JaredCo do you think you can post what ports you needed to unblock so if others encounter the issue they know what to look for?
01-11-2011 08:48 PM
01-11-2011 10:04 PM
Ok, if you ever get around to doing it then post up the ports.
01-12-2011 01:03 AM
if you read this thread completely: Mark Sohm already has posted how to change the ports
01-12-2011 01:18 AM
Woops, my bad. Must have lost it in the five pages. I see it's on page 4. Good to know.