Momentics IDE appears to hang in debug mode

Similar Questions

• QNX Momentics IDE design mode

  Hi people - I just started development in QNX Momentics IDE and I, no matter what I try, doesn't happen in "design" mode  It is disabled, even when training following the exact steps in the video tutorials on web Blackberry based on. Are there cases where the IDE would be denied the opportunity to 'design' when you view a QML file?

  Check the settings of the editor on BlackBerry/QML, uncheck the box "disable", re - open a qml file. It must run the compatibility check.

• Pretty print Qt containers when debugging QNX Momentics IDE

  Hi all

  I wonder if anyone knows how to display the containers in a human readable way under debugging Qt?

  So, IE if I str ("hello") QString under debug I want to see 'Hello' as the value of str instead of lots of pointers

  Thank you

  Philippe

  Yes, you can have the debugger QNX Momentics IDE show the string in the window of variables properly.

  Directions for use:

  Window-> Preferences-> C / C++-> debug-> GDB and make sure that "pretty printing" is enabled

  Make a file called .gdbinit in the folder root of your project and put this:

  Python
  import sys
  sys. Path.Insert (0, '.')
  of qt4 import register_qt4_printers
  register_qt4_printers (no)
  end

  Then copy the qt4.py file from: https://projects.kde.org/projects/extragear/kdevelop/kdevelop/repository/revisions/master/changes/de...

  Place this file in the same working directory (the directory of the project).  Or you can put somewhere else and replace the "." in "sys.path.insert (0, '.').  with the folder that contains the qt4.py

  Next time you run the debugger, it should show the QString.

  If you have any problems (it does not), you can see the gdb trace console and the gdb console (try: source .gdbinit) to see the errors.

  I still have to do with the dinkum STL.   I just started...  PM me if you want that the instructions once I'm done...

  p.s. Thanks to the kdevelop team who made this python module.

  Edit: removed game print pretty line in .gdbinit.  correctly implemented by the ide from qnx.

• Errors appear in the file open in Momentics IDE under the new Cascade

  Hi all

  I created a new waterfall project added a few things like a mapView and it compiled and run yesterday on the emulator. But today when I opened the files it reports errors that it cannot locate the include files, but only, it throws errors once I open the file.

  The kicker is he will be always compile and run on the emulator, as if there are no errors.

  What is a linker or IDE problem? And if anyone knows how to fix this it would be great

  Kind regards

  -J

  Reinstall Momentics IDE seemed to fix the problem. May have been the mistake of the indexer. ?

• Build the project fails on QNX momentics IDE

  Software: Native SDK 2.0 beta3 QNX momentics IDE

  Problem: after press build project, no file bar.

  Have tried these methods:
  a.Restart pc and playbook on failure
  b on blackberry desktop software fail
  invalid c.Check os version
  d.REINSTALL blackberry sdk native-beta3 fail

  Does anyone know how to solve the problem?

  Thank you for your attention.

  Generation of a project does not generate a BAR file.

  Launch (run or debug) an application generates a BAR file development mode.

  Export Release Build Wizard generates an output mode BAR file.

  HTH,

  Christian

• My program works only in debug mode

  Dear all,

  I'm just starting to use LabVIEW and develop a pilot thing.

  The program is rather in order because I only used to work with text-based program.

  The current program works without any error message from debug mode.

  To give an idea of how it is made:

  1. configure the serial port settings (address of the machine, baud rate, parity, etc.)

  2. send to the instument the name of a short to run program.

  3 send commands of mutiple string instruments.  These channel commands build a short program to control the instrument.

  4 send another command string to run the short program

  The problem is that it does not work in enforcement mode.  It seems to me that the communication between the device and the computer seems to be too fast.

  Given that the program is designed in a sequential manner, not have a loop while or do loop so I can not add any timing function.

  Could someone give me a tip or a good direction for this problem?  It would be really appreciated.  Thank you.

  You could do something like the amendment attached. Note how I modified the component of connector for the Subvi in the classic 4-2-2-4 operating mode and notice where I connected the terminals.

  NOTE: I guess that the VI is supposed to work only once, and that you do not use the continuous run button in the toolbar. You're not, are you?

• The code works in debug mode but crashes when compiling in release mode

  I am facing the following problem. I have code that works well when it is run in debug mode. However, when I compile it in release mode and run the executable file, code freezes and does not work. The code acquires images from a camera of Hamamatsu. In debug mode, I'm able to acquire images permanently. However, in the release version, the code crashes after the acquisition of the first image.

  I use version 7 of LabWindows/CVI.

  I would be very happy if I can get any help/suggestions for this problem?

  Thank you!

  Kind regards

  Kaddour

  Neji:

  If you search this forum for "version crash debug" or "release version crash" or other similar expressions, you will find that it is a fairly common question.  Look through the other posts that you find here to see if something applies to you.

  The debug version does a few things like padding variable, then you can sometimes invaded your space variable declared without crushing the next variable.  In the statement, the variables are packed, so if you invaded one, you replace another.  Just a possible difference.

  You can do some things in your exit code to see where things get lost, as (temporarily using printf after several instructions at beginning and end of your loop to try to identify this failure of line of code.)

  Look through other threads for other ideas.

• Debug mode - adb driver problem

  Hello

  I can't connect my phone to my PC in debug mode. It seems that the adb interface drivers cannot be installed correctly. Whenever I connect my phone, the following entry appears in the Device Manager:

  

  I activated the developer mode and usb debugging. Adb devices running in the command prompt shows no device. I also tried two other xperia (older models) phones to connect to my PC, and both were instantly detected. I tried to reinstall the drivers for my phone and I tried to use adb tool install tool (link), but it does not solve the problem. The phone works very well in MTP mode and I can transfer files to it without problem.

  My operating system is Windows 7 x 64.

  Can someone help me please?

  In fact, it seems that there is a problem with the driver. I will pass this internally.

  But you can try (worked for me in W7 x 64) is to download the driver here: http://developer.android.com/sdk/win-usb.html#top and unzip it into a folder.

  Then update the driver in Device Manager but select manual installation, 'Have disk', select 'android_winusb.inf', then "Android ADB Interface". I can connect to my M4 Aqua on ADB after installing this driver.

• Momentics IDE not pair deveice using wifi

  I use momentics ide connect via wifi q10, previously, I still do and normal use. but now I can not connect. would it still have the error message 443 has expired, although I did activate the mode of development and use IP, someone please help me with

  You get a response if you ping the IP? Also double-check of parameters you are using IP address.

• Is it possible to rename devices in Momentics IDE

  Hello!

  I develop native applications with Momentics (Cascades) IDE on my MacBook Pro.

  With the new Momentics IDE 2.1, it is very easy to connect multiple devices to the computer and link them with the IDE.

  But the way in which the names of devices appears in the Momentics "on:" drop-down list is not very useful.

  Some of these related devices is the name of the device under 'Settings', but some of them get only "blackberry -" where are the last 4 digits of the PIN device. With this information, it is very difficult to know what entry in the list is what device (I have attached a Q5, a passport and a Z10 at the same time).

  Is it possible to rename the entries manually (as "black Q5', 'white Z10',... or something like that)?

  Thank you!

  Can't you see devices in the Project Explorer? It should be possible to rename the devices, just like any other project.

  Otherwise, try the view of devices (could be hidden however).

• Pitfall in Momentics IDE error

  I get an error in Momentics IDE thanks to which the build gets stuck. I even tried to reinstall Momentics but it does not help.

  The shows of building progress
  :

  Calling command: make - j2-Debug

  and it stays like that... it crashes every time that 28%...

  Help, please!

  Thank you

  IndiDeveloper >

  That's good news. Don't forget to mark your last such post only accepted while others will know that you have found a solution.

  IndiDeveloper wrote:

  The problem has solved bene!

  I was porting Android code so it 'public' specifier before the function in the CPC to access file. On the withdrawal that the build succeeded.

  Thanks for your help!

• Clean install QNX Momentics IDE but no. SDK can be found.

  I unstall the old version, delete the folder and install the QNX Momentics IDE in the default directory;

  When I try to create a workspce, it appears without SDK is located. Install a software development kit to enable the QNX Momentics features.

  Anyone has the same problem?

  Found the problem

  in the windows--> the Blackberry SDK native short cut tap

  C:\bbndk\ide\win32\x86\eclipse\qde.exe

  To take

  C:\bbndk\bbndk.bat (bbndk_admin.bat)

  Then the problem is resolved.

• Momentics IDE installation problems

  I tried today to use QNX Momentics IDE 10.2.0.115 on OS X 10.9 and I get FMV related issues.

  Here is this that java-version on my machine says:

  java version "1.7.0_45"
  Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
  Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
  

  And here's what error I get when I run qde:

  2013-10-29 20:53:31.941 qde[2082:507] Error loading /Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/MacOS/libjli.dylib:  dlopen(/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/MacOS/libjli.dylib, 265): no suitable image found.  Did find:
  /Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/MacOS/libjli.dylib: mach-o, but wrong architecture
  

  It looks like so there is an inconsistency that the IDE expects 32-bit JVM so that my computer is the 64 bit one.

  We should expect the IDE to run on a 64-bit JVM?

  After more frustrating google search I came to the conclusion that my JVM was strictly 64 bit and that the IDE runs only on 32-bit.

  Initially, I downloaded the Oracle's JVM and apparently it comes in 64-bit only. I then installed the Apple Java from http://support.apple.com/kb/DL1572 and now I am running

• Development of extensions for Photoshop CC2015 (Mac). Debug mode?

  I'm new to the development of Photoshop plug-ins and will have difficulty to get my plugin test appears in Photoshop.  I get the error message "extension < name > could not be loaded because it was not signed."  Now, I understand that you are supposed to put your machine in debug mode, then you can ignore the signature verification (I added < key > PlayerDebugMode < / key > < String > 1 < / string > to Library/Preferences/com.adobe.CSXS.5.plist) but I still got the error.  What Miss me?

  Ah, found on page 11 of CC14_Extension_SDK.pdf:

  • In OS X 10.9 Apple introduced a cache mechanism for property list files. This means that property changes do not take effect immediately. For force you the change is taken into account, open the Terminal application and enter the following command:

    sudo killall cfprefsd

• Debug mode does not

  Hello
  
  We are in the process of migration of the APEX v3.2.1 on the database 10 g to v4.2.1 on database 11 g. APEX APEX is installed fresh on 11g. I was testing imported and exported of v3.2.1 application in v4.2.1. I was not able to activate the debug mode in the developer bar when the application runs. The url changes, but no debug information appears as was the case in v3.2.1. I see a partial set of debugging information when I open then see the debug window in the bar of developer. This show of debugging is incomplete. By that I mean I don't see not session state change and I don't see any information in the function "wwv_flow.debug".
  
  I read in a thread for an earlier version 4, toggle the debug field in edit application properties and apply, but that no longer works. Something to note is that when the debug field in edit application properties was set to NO, I don't have the error "Debugging is not enabled for this application" when you turn on the debug mode.
  
  I created a zero of application form and debug mode does not work either.
  
  There is a global setting in administration somewhere I should activate to get debug information in the page as in v3.2.1?

  dominiquefortin wrote:

  We are in the process of migration of the APEX v3.2.1 on the database 10 g to v4.2.1 on database 11 g. APEX APEX is installed fresh on 11g. I was testing imported and exported of v3.2.1 application in v4.2.1. I was not able to activate the debug mode in the developer bar when the application runs. The url changes, but no debug information appears as was the case in v3.2.1.

  No debug information appears online in the APEX 4.x page. All of this appears in the debug window.

  I see a partial set of debugging information when I open then see the debug window in the bar of developer. This show of debugging is incomplete. By that I mean I don't see not session state change and I don't see any information in the function "wwv_flow.debug".

  Note that the debug window contains an interactive report that applies a default filter for the last visited page. You might not see the report of the desired page. Remove the filter from the page to see all the currently available debug reports. There are also separate reports for each page show/accept, then make sure that you select the correct phase.

  I read in a thread for an earlier version 4, toggle the debug field in edit application properties and apply, but that no longer works. Something to note is that when the debug field in edit application properties was set to NO, I don't have the error "Debugging is not enabled for this application" when you turn on the debug mode.

  I think maybe I saw a bug for this, but I can't find a reference at the moment.

  There is a global setting in administration somewhere I should activate to get debug information in the page as in v3.2.1?

  N ° all debugging information are now displayed in the debug window.