Debugging of the Frustrations

Similar Questions

• How to get DEBUGGING into the command prompt

  I got to the House and I need to play with DEBUGGING in the CMD.  However, whenever I type "debug" in cmd, I get the following message:

  "A 'DEBUG' is not recognized as a command internal or external, an executable program or batch file."

  I also tried to run CMD as administrator, but that did not help.

  How to enter DEBUG?

  Hello

  By default what is Debug:

  'C:\Windows\System32\debug.exe '.

  You need an assembler.

  This question would be better asked in the MSDN Forums.

  MSDN
  http://msdn.Microsoft.com/en-us/default.aspx

  MSDN - where is the Forum for...
  http://social.msdn.Microsoft.com/forums/en-us/whatforum/threads

  MSDN - Forums
  http://social.msdn.Microsoft.com/forums/en-us/categories

  Assembly language
  http://en.Wikipedia.org/wiki/Assembly_language

  Freebyte's Guide to... Assembler free programming
  http://www.Freebyte.com/programming/assembler/

  Programming in assembler
  http://www.cs.uakron.edu/~margush/306old/index.html

  Using the Microsoft Windows Debugger (WinDbg)
  http://kipirvine.com/ASM/4th/debug/WinDbg/index.htm

  WinDbg
  http://en.Wikipedia.org/wiki/WinDbg

  Download and install the debugging tools for Windows
  http://www.Microsoft.com/whdc/devtools/debugging/default.mspx

  OllyDbg
  http://www.OllyDbg.de/

  The place on the net to learn Assembly
  http://homepage.Mac.com/randyhyde/Webster.cs.UCR.edu/index.html

  I hope this helps.

  Rob Brown - MS MVP - Windows Desktop Experience: Bike - Mark Twain said it right.

• Debugging on the device?

  Newbie here. I'm finally able to debug on a real device, 9330 which shows:

  6.0 bundle 2333 (v6.0.0.524, platform 4.4.0.438)

  I write apps targeting the 5.0 SDK. I guess from the above that the camera itself is version 6.0.0.524, is this correct?  So where can I get the specific Simulator for this?  None of the 4 last digits Curve 9330 simulators match. (I am trying to eliminate all the 'cannot find debug file"nonsense!) is there any detailed white papers on debugging on the correct device?  Also, I try to use Eclipse.

  Thanks in advance!

  All available BlackBerry smartphone simulators are available for download here: http://us.blackberry.com/developers/resources/simulators.jsp

  It may not be a release of Simulator for all versions available for download.  But we are always adding more, so you can keep an eye on this page for updates.

• Debugging on the issue of the device!

  Beginner again. My Java application with my new Plugin Eclipse 1.5.2 on win7/64 and loving debug so far and I have used a simulator 9330. I've implemented a new program feature that works fine on the Simulator, but when I Pack the app and deploy on a device 9330, it explodes with an error "index out of range". In order just to shoot this, I just use the option "Debug/Blackberry Device" and set breakpoints in the code of my program. This allows me to pass her and is very well. I found that the problem is on my side of the fence (code/design) but when I'm debugging on the device itself I do not see the values of the objects/properties, I get "

  " when I try to INSPECT an object.property.

  The big question: is it possible to debug on a device and see all the object.property values that scroll us? If yes how?

  Thanks in advance!

  Yes, it is possible but requires the files for your device BlackBerry OS .debug.  When you have started debugging you should have been prompted to download files of debugging.  Did you say yes to that?  If yes then automatically download the required files.  If you click on no, you will not be able to use debugging features.

• debugging on the actual device different subversions jde - firmware

  I want to debug my code on a device connected via usb. I know that I need the same type in JDE and the device.

  For example, JDE 4.5-> device must have firmware 4.5.

  Although I checked the debugger tells me it can't find net_rim_app_manager.debug and many others. When I browse with browse for the files of simulator of the JDE debug files it is not like that and told me

  Bad debug information: \simulator\net_rim_app_manager.debug(4846a5e2)-net_rim_app_manager(494996a0)
  

  My regognizes JDE-attachment-device usb. When I ignore the mistakes I see some, but not all of the messages in the debug window. If the connection is ok.

  My firmware installed JDE Simulator Version DO match the firmwareversion of the unit BUT not the firmware-sub-version number. I mean the numbers after the second point (4.5.XXXX) is the reason for the error message?

  If Yes,

  -How and where can I get the EXACT match firmware-subversion for my device?

  -How can I do a real device debugging with the latest firmware?

  If none, I miss something else?

  my JDE:4.5.0

  my camera - 4.5.0.Simulator - JDE: 8310

  my JDE - 4.5.0.Simulator - Firmware: 4.5.0.44

  my real device: 8310

  my real device Firmware: 4.5.0.124

  Thanks for help

  Anil

  OK, after some research and debugging, I found the solution in this post

  http://supportforums.BlackBerry.com/Rim/Board/message?board.ID=java_dev&message.ID=3769&query.ID=266...

  a little summary here (including the above mentioned display comments). In this example, we assume that you are using JDE 4.5.0.

  • Check that you have installed the latest BlackBerry-Desktop-Manager. So you can be sure, that your device connected by usb is detected
  • Versions have to mach exactly! When you have the 4.5.0.102 firmware on your JDE-Simulator, you MUST have firmware on your real device 4.5.0.102. RIM provides many different simulators with a different firmware for debugging http://www.blackberry.com/developers/downloads/simulators
  • Install the corresponding correct Simulator and follow the Instructions of BB JDE 4.5.0 Guide Chapter development
    "Install the .debug computer files".
  • Connect your real device via USB
  • Compile your code in RIM JDE
  • If you use sensitive APIs-> sign your code
  • Load the cod files compiled on your actual device with JavaLoader.exe
  • Debugging-> attached to him-> Pocket-> USB ()
  • No, you can debug, breakpoints, out of the console, etc...

  Note: Although I have installed now the exact match versions. The debugger tells some files that it "does not find" them which is:

  net_rim_theme_120_green_320x240_b.debugnet_rim_theme_120_green_320x240_b-(1-13).debug
  
  net_rim_theme_120_today_320x240_b.debug net_rim_theme_120_today_320x240_b-(1-13).debug
  
  net_rim_bb_smime.debug
  

  I think that these debug files are relatively large for most applications, so you can ignore it.

  A good indicator to see that there is really a version mismatch is the first file, it cannot find "net_rim_app_manager.debug".

  Anil cordially

• Not be able to debug on the device

  Hi friends,

  I'm not able to debug device now. I have the same version of Simulator, sim even package version as I have on mobile. I've been able to debug a few minutes back, but I had not changed anything just removed app and new thought of debugging to display the value in another function. Even after removing the application, all objects remain in the persistent storage.

  Please help me

  Hi friends I am successfully able to solve. The only thing to do is to clean the Simulator, even if you want to debug on the device. Now, I am able to debug each time that the device suceesfully. Timeout paradigm for everything by retrieving the coordinates that we should create a timer so that elapsed, he should leave the idea of recovering the coordinates.

• Fastest way for debugging on the device of JDE

  Hi all

  I'm new to the development of BB and struggling to find a way to debug on device effectively.  My application has a lot of comm of bluetooth in him so most debugging should occur on the device instead of Simulator (please, correct me if this is not true).  Here's my development/debugging process.

  1. change the code

  2. generate the code

  3. the signal code

  4. connect device to Desktop Manager via the USB cable

  5. delete a previous version of my application

  6. load the latest version of my application

  7. connect to the device using JDE

  8. install a device app

  My quesitons are...

  1 should I sign the code whenever I have rebuild?

  2. is there a more effective way to get the latest version on the device instead of uninstalling then reinstall via Desktop Manager (it takes forever).

  There MUST be a better way.  Thanks in advance to all those who answer.  =)

  1. Yes, you sign cod every time after reconstruction you have for debugging on the device.

  2. you can load application in the device in various ways. If you use the Desktop Manager, you need to go if the steps you mentioned.

  But most developers use javaloader (JDE bin directory) to get the latest version in the device during development.

  To do this, run the following command from the bin directory:

  JavaLoader-u load applicationName.cod

  Also take a look at the article for details on loading the application on the device.

  http://www.BlackBerry.com/knowledgecenterpublic/livelink.exe/fetch/2000/348583/800708/800647/How_To _...

  Concerning

  Bika

• How do you keep the indicator changing hacker to debug in the URL to expose all YES?

  Hello
  How do you keep an indicator changing hacker to debug in the URL to expose YES everyone?
  I have installation of State Protection and it protects the elements on the Page.
  
  Published by: heavy on August 6, 2010 12:12

  Hello

  You can change the attributes of the application
  http://download.Oracle.com/docs/CD/E14373_01/AppDev.32/e11838/BLDR.htm#sthref323

  BR, Jari

• JDeveloper debug: start the automatic extension debugging session

  Hello
  
  I'm trying to start a debugging session from a remote process in the extension. (The idea is that the user simply clicks on a button provided by the extension and remote debugging is started without any other parameters necessary user.)
  From the description of the API, the javax.ide.debug.Debugger class seems to be very promising.
  
  Unfortunately, Debugger.getClientConnector (Context) always throws an UnsupportedOperationException. I have no idea what to do, so my current project supports the operation.
  
  Can anyone help? No results for a search on the net or this forum.
  
  If this is not the right place to ask this question, can someone point me in the right direction?
  
  Thanks, Steffen

  Steffen,

  Now JDeveloper has no support for debugging of the JSR 198 through the javax.ide.debug.Debugger class. I filed a request for improvement for this, and we will implement this in a future release.

  Keimpe Bronkhorst
  Team JDev IDE

• Unhandled exception JIT debugging at the launch of the game

  I always experience this problem when I tried to run my game.

  Tried several methods, including 'clean start up', but I'm still having the same problem.

  See the end of this message for details on the call
  just-in-time (JIT) debugging instead of this dialog box.

  The exception text *.
  System.Runtime.InteropServices.SEHException: External component has thrown an exception.
  to BmLauncherLib.PhysXSDK. {ctor} (PhysXSDK *)
  to BmLauncherUtils.PhysXSDK... ctor()
  at BmLauncher.Settings.DetermineDefaultPhysXLevel)
  to BmLauncher.Settings.StaticInitialise (IniFile iniFile IniFile iniEng, iniInst IniFile, SystemInfo sysInfo, String localePath, String localeConfigFile)
  at BmLauncher.Form1.Initialise)
  at BmLauncher.Form1.OnLoad (Object sender, EventArgs e)
  at System.Windows.Forms.Form.OnLoad (ByVal e As EventArgs)
  at System.Windows.Forms.Form.OnCreateControl)
  at System.Windows.Forms.Control.CreateControl (Boolean fIgnoreVisible)
  at System.Windows.Forms.Control.CreateControl)
  at System.Windows.Forms.Control.WmShowWindow (Message & m)
  at System.Windows.Forms.Control.WndProc (Message & m)
  at System.Windows.Forms.ScrollableControl.WndProc (Message & m)
  at System.Windows.Forms.ContainerControl.WndProc (Message & m)
  at System.Windows.Forms.Form.WmShowWindow (Message & m)
  at System.Windows.Forms.Form.WndProc (Message & m)
  at System.Windows.Forms.Control.ControlNativeWindow.OnMessage (Message & m)
  at System.Windows.Forms.Control.ControlNativeWindow.WndProc (Message & m)
  at System.Windows.Forms.NativeWindow.Callback (IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

  Loading assemblies *.
  mscorlib
  Assembly version: 2.0.0.0
  Win32 Version: 2.0.50727.8000 (FX35W81RTMGDR.050727 - 8000)
  Code: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
  ----------------------------------------
  BmLauncher
  Assembly version: 1.0.1.0
  Win32 version: n/a
  CodeBase: file:///C:/sggameworlddata/3571930906039371546/%F2%F9%F2%F0%CF%C0_%B0%A2%B8%CA%B7%E8%C8%CB%D4%BA%BC%F2%CC%E5%D6%D0%CE%C4%C4%EA%B6%C8%B0%E6(%BA%BA%BB%AFV1.2)(%C3%E2xlive)/10102813/10102813/Binaries/BmLauncher.exe
  ----------------------------------------
  System.Windows.Forms
  Assembly version: 2.0.0.0
  Win32 Version: 2.0.50727.7905 (win9rel.050727 - 7900)
  Code: file:///C:/windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
  ----------------------------------------
  System
  Assembly version: 2.0.0.0
  Win32 Version: 2.0.50727.7905 (win9rel.050727 - 7900)
  Code: file:///C:/windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
  ----------------------------------------
  System.Drawing
  Assembly version: 2.0.0.0
  Win32 Version: 2.0.50727.7905 (win9rel.050727 - 7900)
  Code: file:///C:/windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
  ----------------------------------------
  System.Management
  Assembly version: 2.0.0.0
  Win32 Version: 2.0.50727.7905 (win9rel.050727 - 7900)
  Code: file:///C:/windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
  ----------------------------------------
  BmLauncherUtils
  Assembly version: 1.0.0.0
  Win32 version: n/a
  CodeBase: file:///C:/sggameworlddata/3571930906039371546/%F2%F9%F2%F0%CF%C0_%B0%A2%B8%CA%B7%E8%C8%CB%D4%BA%BC%F2%CC%E5%D6%D0%CE%C4%C4%EA%B6%C8%B0%E6(%BA%BA%BB%AFV1.2)(%C3%E2xlive)/10102813/10102813/Binaries/BmLauncherUtils.DLL
  ----------------------------------------
  msvcm80
  Assembly version: 8.0.50727.8428
  Win32 version: 8.00.50727.8428
  Code: file:///C:/windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d/msvcm80.dll
  ----------------------------------------
  System.Xml
  Assembly version: 2.0.0.0
  Win32 Version: 2.0.50727.7905 (win9rel.050727 - 7900)
  Code: file:///C:/windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
  ----------------------------------------

  JIT debugging *.
  To enable just-in-time (JIT) debugging, the .config file for this
  application or computer (machine.config) must have the
  jitDebugging value set in the system.windows.forms section.
  The application must also be compiled with debugging
  permit.

  For example:

  
     
  

  When JIT debugging is enabled, an unhandled exception
  will be sent to the JIT debugger registered on the computer
  rather than be handled by this dialog box.

  Hello

  Thanks for posting your question on the Microsoft community.

  I would like to know some information about the problem so that we can help you better.

  You made any hardware or software changes on your computer before the show?

  Thank you for details on the question and your efforts to resolve.

  This behavior can occur if the JIT debugging is enabled or due to corrupted registry files.

  Please refer to the suggestions of Shinmila H said on February 14, 2010 and check if it helps.
  http://answers.Microsoft.com/en-us/Windows/Forum/Windows_7-windows_programs/JIT-debugging/36c33bc7-5071-4b9b-a689-d49e6191ece1

  Note: Serious problems can occur if you modify the registry incorrectly. Therefore, make sure that you proceed with caution. For added protection, back up the registry before you edit it. Then you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click on the number below to view the article in the Microsoft Knowledge Base:
  http://Windows.Microsoft.com/en-us/Windows7/back-up-the-registry

  I hope this information helps.

  Please let us know if you need more help.

  Thank you

• cannot debug on the last Simulator

  Windows 7:

  10.0.10.261 SDK

  10,261 Simulator

  Every time start to debug an application generated by the wizard got an error:

  Error in the final launch sequence
  Impossible to prepare and upload the binary file
  Failure of deployment: Info: request shipment: install and launch
  Info: Action: install and launch
  News: Native debugging: on
  Info: File size: 288372
  Info: Installing com.example.test.testDev_xample_test3083a1e3...
  Info: Treatment 288372 bytes

  I was faced with the same question, but the following works for me.

  1. uninstall the Simulator completely (remove VMWare records)

  2. install a new copy of the Simulator.

  3. be sure that you have built your application successfully before you run it on a simulator.

  4. first of all try to run your application without debugging if you get success then try for debugging.

  Note: Please do not change any setting in the Simulator, especially the time and Date just confirm that if the development Mode is enabled or disabled. If he is out to turn it on.

  Hope this works for you.

  Concerning

  Muhammad Faheem Amjad

• Debugging of the native part of an extension of Webworks

  Dear all,

  is it possible to debug webworks extensions in order to discover the errors?

  We often (and randomically) get the common load error 'cannot find error need. "

  / usr/lib/etc. Library not found", but we can't manage how to discover more information about this...

  Other than the error itself, I unfortunately discovered that debbuging is really a pain in this scenario...

  Any help or advice of BB guys is really appreciated!

  Thank you very much

  -marco

  Hi Marco, native debugging Extensions is currently very difficult, due to their hybrid nature.

  I usually create a native C++ application first, work and then make a native extension. Have you tried?

  See you soon,.

  A

• Debugging in the Release version

  Hello world

  my new app uses a card to process the data. The data processor triggers a signal and slot this respons by closing the card. Well, at least while debugging. I tried the release just before you download for the BlackBerry World and I noticed that the card don't be closed. Data are transformed very well, but somehow the signal is not properly raised or the card cannot be closed. I have attached a bit of code to illustrate my operation.

  The processing of the data

  void WebpageFetcher::done()
  {
      DbHelper* dbHelper = DbHelper::getInstance();
      dbHelper->insert(some data);
      //Signal that we're done!
      emit fetchDone("Success!");
      delete dbHelper;
  }
  

  The Application

  fetcher = new WebpageFetcher(uri);
  connect(fetcher, SIGNAL(fetchDone(QString)), this, SLOT(fetchingDone(QString)));
  

  void ApplicationUI::fetchingDone(QString msg)
  {
      // Assemble message
      CardDoneMessage message;
      message.setData(msg);
      message.setDataType("text/plain");
      message.setReason("Success!");
      // Send message
      m_invokeManager->sendCardDone(message);
  }
  

  Now my question is: How can I see the output in Release version? qDebug will obviously not work, but I need a tool to help me understand this issue.

  Looks like the culprit was "build automatically" neglected my amendments to the code for the Release version. Although 4 wasted hours, could be worse

• Device debugging for the camera application

  Hello

  I would like to perform device debugging for my camera application.

  Problem is that my application seems to work fine on the emulator, but I do not get the desired result on the device.

  But when I try to debug the application I can't access the camera. Whenever I try to access the camera or any other multimedia file I get a warning that I need to first unplug the unit.

  Any suggestions would be very helpful.

  Thank you

  Saket

  Hi, if you want to access a file media, first of all, go to options > memory > mass storage Mode support > power off.

  and now try to debug your application.

  PD: Sorry for my English.

• "Enter password" calls while debugging using the 4.2.2.66 (8830-Verizon) Simulator

  If I click on "Start the Simulator" the Simulator works well, but I'm trying to connect to a debugger, I get the following message:

  Password

  If I don't get anything, the debugger connection times out.   I tried things like "password" and "blackberry", and the debugger just disconnects.  I've debugged using dozens of other simulators, and I have never seen it before.

  Anyone know why this is happening?

  Thank you
  Mark

  I believe that I have found a workaround.  I use the 4.2.1 JDWP.  If I use the JDWP 4.7.0 instead, I do not receive the password, and the debugger attaches successfully.