Hello,
actually I was quite surprised myself to realize this yesterday - so I would like to share this information with you.
With a lot of the new Simulators (that I have installed separately) I have the issue, that I actually can't debug my applications any longer simply cause the Eclipse IDE runs into a timeout when trying to attaching the debugger. [I am running Windows7 (64bit) on a i7 with 4GB of RAM - so it's not necessarily a hardware problem ]
The IDE is displaying a massage like:
'Launching [mySimLauncherNameHere]' has encountered a problem. Failed to connect to remote VM. Connection timed out .
If you also have the message:
Some debug information is missing. Not all applications may be debuggable. Please ensure that you have installed the simulator package that matches the handheld code you are attempting to debug
() Don't ask me again
Of course sometimes there are missing debug info in the simulator directory caused by broken deployments of my apps - but all of the new Simulators that can be downloaded from RIM does not include ALL required debug information from the default installed applications. E.g. here is a list of the console output when you try to debug an application in the Torch 9810 7.1.0.432 Sim:
No debug information found for 'net_rim_speech_data_en_US-1' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-2' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-3' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-4' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-5' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-6' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-7' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-8' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-9' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-10' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-11' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-12' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-13' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-14' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-15' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-16' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-17' (4f5beb1b).
No debug information found for 'net_rim_speech_data_en_US-18' (4f5beb1b).
No debug information found for 'net_rim_bis_client__en' (4f3c2674).
No debug information found for 'net_rim_bis_client__en-1' (4f3c2674).
No debug information found for 'net_rim_bis_client__en-2' (4f3c2674).
No debug information found for 'net_rim_bis_client__en-3' (4f3c2674).
No debug information found for 'net_rim_bis_client__en-4' (4f3c2674).
No debug information found for 'net_rim_bis_client__ko' (4f3c2701).
No debug information found for 'net_rim_bis_client__ko-1' (4f3c2701).
No debug information found for 'net_rim_bis_client__ko-2' (4f3c2701).
No debug information found for 'net_rim_bis_client__zh_TW' (4f3c2797).
No debug information found for 'net_rim_bis_client__zh_TW-1' (4f3c2797).
No debug information found for 'net_rim_bis_client__zh_TW-2' (4f3c2797).
No debug information found for 'net_rim_bis_client__id' (4f3c26df).
No debug information found for 'net_rim_bis_client__id-1' (4f3c26df).
No debug information found for 'net_rim_bis_client__id-2' (4f3c26df).
No debug information found for 'net_rim_bis_client__zh_CN' (4f3c278a).
No debug information found for 'net_rim_bis_client__zh_CN-1' (4f3c278a).
No debug information found for 'net_rim_bis_client__zh_CN-2' (4f3c278a).
No debug information found for 'net_rim_bis_client__pt_BR' (4f3c273a).
No debug information found for 'net_rim_bis_client__pt_BR-1' (4f3c273a).
No debug information found for 'net_rim_bis_client__pt_BR-2' (4f3c273a).
No debug information found for 'net_rim_bis_client__en_GB' (4f3c2680).
No debug information found for 'net_rim_bis_client__en_GB-1' (4f3c2680).
No debug information found for 'net_rim_bis_client__en_GB-2' (4f3c2680).
No debug information found for 'net_rim_bis_client__fr' (4f3c26a0).
No debug information found for 'net_rim_bis_client__fr-1' (4f3c26a0).
No debug information found for 'net_rim_bis_client__fr-2' (4f3c26a0).
No debug information found for 'net_rim_bis_client__th' (4f3c2768).
No debug information found for 'net_rim_bis_client__th-1' (4f3c2768).
No debug information found for 'net_rim_bis_client__th-2' (4f3c2768).
No debug information found for 'net_rim_bis_client__es' (4f3c268b).
No debug information found for 'net_rim_bis_client__es-1' (4f3c268b).
No debug information found for 'net_rim_bis_client__es-2' (4f3c268b).
No debug information found for 'net_rim_bis_client__pt' (4f3c272e).
No debug information found for 'net_rim_bis_client__pt-1' (4f3c272e).
No debug information found for 'net_rim_bis_client__pt-2' (4f3c272e).
No debug information found for 'SecurIDLib' (456c5107).
No debug information found for 'net_rim_bis_client_resources' (4f3c27a7).
No debug information found for 'net_rim_bis_client_res' (4f3c27a2).
So my observation was, as more debug information is missing as longer the attaching debugger process is running - causing more likly the attaching process would fail cause of the timout.
Even if the 'missing debug information" dialog comes with a "Don't aks again' checkbox this setting is not persistent of an IDE restart...
So how to solve this?!
Each installed RIM ejde.componentpack comes with a definition where you can declare missing debug information files.
The file which contains this declaration is called FixedBuild.rc You find this file in the following directory:
[ECLIPSE_IDE_HOME-DIR]\plugins\net.rim.ejde.componentpack[VERSION]\components\bin
e.g. as example:
C:\DEV\ide\eclipse3.6\plugins\net.rim.ejde.componentpack7.0.0_7.0.0.6\components\bin
- So close Eclipse (if it's already running)
- Make a backup of the original FixedBuild.rc file
- Open the FixedBuild.rc file with a text editor like Notepad (or Notepad++)
- Check if you file have already a section called: 'MissingDebugInfoAllowed'
- If it's present just add the listed missing cods from the console output to the list, if your FixedBuild.rc files does not contain such a section paste one in there:
[MissingDebugInfoAllowed
SheetToGo
DocsToGo
WordToGo
SlideshowToGo
THK2
SecurIDLib
Klondike
Sudoku
VZNavigator
SMSWakeUp
MOD
net_rim_speech_data_en_US
net_rim_bb_gmail
net_rim_bb_gmail-1
net_rim_bb_gmail-2
net_rim_bb_gmail-3
net_rim_bb_gmail-4
net_rim_bb_gmail-5
net_rim_bb_gmail-6
net_rim_bb_gmail-7
net_rim_bb_gmail_help_it
net_rim_bb_gmail_help_fr
net_rim_bb_gmail_help_es
net_rim_bb_gmail_help_pt_BR
net_rim_bb_gmail_help_pt
net_rim_bb_gmail_help_de
net_rim_bb_gmail_help_nl
net_rim_bb_gmail_help_en
net_rim_bb_gmail_resource__fr
net_rim_bb_gmail_resource__de
net_rim_bb_gmail_resource__ed
net_rim_bb_gmail_resource__it
net_rim_bb_gmail_resource__nl
net_rim_bb_gmail_resource__pt
net_rim_bb_gmail_resource__pt_BR
net_rim_bb_gmail_resource__en
net_rim_bis_client__en
net_rim_bis_client__en-1
net_rim_bis_client__en-2
net_rim_bis_client__en-3
net_rim_bis_client__en-4
net_rim_bis_client__ko
net_rim_bis_client__ko-1
net_rim_bis_client__ko-2
net_rim_bis_client__zh_TW
net_rim_bis_client__zh_TW-1
net_rim_bis_client__zh_TW-2
net_rim_bis_client__id
net_rim_bis_client__id-1
net_rim_bis_client__id-2
net_rim_bis_client__zh_CN
net_rim_bis_client__zh_CN-1
net_rim_bis_client__zh_CN-2
net_rim_bis_client__pt_BR
net_rim_bis_client__pt_BR-1
net_rim_bis_client__pt_BR-2
net_rim_bis_client__en_GB
net_rim_bis_client__en_GB-1
net_rim_bis_client__en_GB-2
net_rim_bis_client__fr
net_rim_bis_client__fr-1
net_rim_bis_client__fr-2
net_rim_bis_client__th
net_rim_bis_client__th-1
net_rim_bis_client__th-2
net_rim_bis_client__es
net_rim_bis_client__es-1
net_rim_bis_client__es-2
net_rim_bis_client__pt
net_rim_bis_client__pt-1
net_rim_bis_client__pt-2
net_rim_bis_client_resources
net_rim_bis_client_res
]
As you see in this example there there had been plenty of files already listed here (like SheetsToGo or the gmail client - so I just have added the reported missing debug info files at the end.
- Now save the file...
- Launch Eclipse and start the debugger with the component pack version you just have modified
With this modification most of the modern simulators are running fine now inside my Eclipse and I can continue to develop and debug OS7.x applications without System.out.println debugging!
As a final note I found some interessting Thread here in the forum dealing with "how to adjust debug timeout and the used ports" here: Debugger Failed to connect to remote VM. Connection refused. it might contain additional valueable information for you (even if the accepted solution is not very nice (complete fresh reinstall) - but the thread itself have some really valuable information).
Happy java coding!
Matthias
PS: be so kind and give Credit's if you find this helpful
[FileScout] | [iMazing] | [GPSLogger II] | [Iconify] | [TOMPlayer]
