Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
05-12-2009 10:01 PM
I'm using BlackBerry Plug-in for Eclipse (I have JDE 4.5.0 and 4.6.0 installed). I have a Bold and a Pearl 8220.
I'd like to debug my application using the option "Debug as" and then "BlackBerry device" but I get the following error message. So it seems that I need to install some files in order to proceed with this debug. Can you help me with this?
"No debug information found for module 'net_rim_cldc'. Many debugging features will not work properly."
05-12-2009 10:21 PM
Everybody gets this, don't worry about it.
You can still set breakpoints and single-step code, and you can see the Sytem.out.println() trace from the device in your console window.
05-13-2009 03:15 AM
05-13-2009 03:33 PM
Not sure what I'm doing different from yesterday this time but when I click Debug As and then Blackberry Device it asks for by Bold 9000 password and then it renders the following error message: "The net_rim_app_manager_debug" file is missing. Please choose the missing file." Then it gives me 4 options: Search, Browse, Cancel and Don't Ask this Again. If I hit cancel hundreds of other similar messages will render: "net_rim_app_manager_CLDC", "net_rim_app_manager_CDLC-4.Debug", etc...and if I hit Don't ask this again it apparently runs but it won't allow my to do anything apart from "Terminating" or "Disconneting to the device". Also, nothing happens with the device.
I suspect there is really something missing.
05-14-2009 10:47 AM
This is caused by your development enviroment not having a simulator for the operating system on your device.
Look at your device, get the full 4 touple os, 188.8.131.52 for example which was the at&t gold build, go to this web set : https://www.blackberry.com/Downloads/entry.do?code
select the base (likely 4.6.0) and look for the specific number. If your running any of the leeked OSes you are unfortuantly not going to be able to find it here, because this is only for publicly released OSes.
once you have downloaded and installed the OS i don't know 100% how to tie it into eclipse, it may install cleanly, it may not. In the JDE sometimes you need to add a new simulator pointing to the installed dir.
05-17-2009 10:18 AM
I downloaded "BlackBerry_Simulators_184.108.40.206_8220.exe" to try in my Pearl 8220 device but weirdly when I run this .exe file a MS-DOS screen pops up for 1 second and that's all! Nothing else happens! It was supposed to install normally as any other device software correct? Do you know if there is any special trick to install it?
05-17-2009 05:28 PM
I would try redownloading it, it seems your copy might be bad. Alternatively you could try running it from the command line so you can see the error. I have also had issues with blackberry installers where I get an error message after they extract and I need to go into temp files and run the msi in there, however I believe that is an issue with my system and not RIM.