Impossible to compile of the SMU-8101 Code

Similar Questions

• Impossible to compile using the beta 2 release

  When I read that Beta 2 is out, I immediately had to download, install and try yesterday. Unfortunately I can not compile more

  I always get the error:

  dyld: library not loaded: libQtXml.4.dylib

  Applications/bbndk-10.0.6-beta/host_10_0_6_1/Darwin/x86/usr/bin/lupdate.. .Pro

  Referenced from: /Applications/bbndk-10.0.6-beta/host_10_0_6_1/darwin/x86/usr/bin/lupdate

  Reason: image not found

  make [1]: leaving directory '... / source/bb10/translations.

  make [1]: * [update] Trace/BPT trap: 5

  make: * [Makefile] error 2

  I found a file called libQtXml.4.dylib, so I don't understand why it does not...

  Try the following command.
  1. open the Terminal application

  CD/Applications/bbndk
  ln-s target_10_0_6_384 / target

  In my case, it worked well.

  symbolic link host_10_0_6_1/Darwin/x86/usr/lib/libQtXml.4.dylib/libQtXml.4.dylib is wrong.

  host_10_0_6_1/Darwin/x86/usr/lib/libQtXml.4.dylib->... /... /.. /.. /.. /Target/Darwin/x86/usr/lib/Qt4/lib/libQtXml.4.8.0.dylib

  I think that it is correct
  host_10_0_6_1/Darwin/x86/usr/lib/libQtXml.4.dylib->... /... /.. /.. /.. /target_10_0_6_384/Darwin/x86/usr/lib/Qt4/lib/libQtXml.4.8.0.dylib

• software installed impossible to associate with the adobe ID code

  I installed, enter the serial number and registered Adobe Lightroom 5 on my MacBook Pro (2.6 GHz Intel Core i7).

  When I click on the icon of the software it take me back to enter a serial number and registration. When I check the software associated with my Adobe ID, Lightroom does not.

  What can I do?

  I solved the problem through to change the permissions on my hard drive. Thank you

• Impossible to DW5. get the U44M1P7 error code

  Product approved and PAID for.

  This error code means some files are missing in your installation.   Have you purchased CS5 from Adobe?  Installation failed. Error U44M1P7 | Updates

  Nancy O.

• Update of LabVIEW, which updated 9.8 DAQmx. SMU-8101 to 9.4 DAQmx. Difficult how?

  I am trying to use MAX to navigate up to a DAQ SMU-6363 connected to my SMU - 8101 RT connected to my local network, but encounters an error: "error-88716 occurred at communication·entre·dispositifs·de·sante·personnels, or the possible reasons: the requested operation failed because a driver on the local and remote system versions are different."  Updated the driver for versions on both systems are the same.  "Remote system: 172.17.2.65, Incompatible driver: NI - DAQmx Device Driver 9.4.0f0.

  This problem occurred recently when I've updated LabVIEW on my development computer to the latest version (2013 f2), which updated DAQmx on my development for v9.8 machine.

  While I'm not quite there, I intend to analyze an audio signal using the SMU-6363.  I guess I'll need to have all the properly information in MAX before I have a hope of implementation in LabVIEW.

  I am now updating the drivers / firmware on the SMU help system full of communication between my development system and the SMU system and having problems.

  During an attempted 'Select all to install' for 'NOR-DAQmx 9.8.0"in the" Add/Remove software"on the SMU-8101 thanks MAX system, I get the error:

  ---------------------------

  Cannot continue following unresolved dependencies:

  Acquiring dynamic signals 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  Acquiring dynamic signals 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  Counter/Timer 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  Counter/Timer 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  NOR-DAQmx 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  NOR-DAQmx 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  Multifunction 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  9.8.0 multifunction data acquisition requires Intel 8254 x Ethernet Driver 5.0
  CompactDAQ 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  CompactDAQ 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  CompactDAQ 9.8.0 requires LabVIEW time real 12.0.0
  E/s digital industrial 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  E/s digital industrial 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  Analog output series 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  Analog output series 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  OR-653 x 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  OR-653 x 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  SC Express 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  SC Express 9.8.0 requires Intel 8254 x Ethernet Driver 5.0

  ---------------------------

  This dialog box does not offer an option to automatically try to download or to locate the missing packets.  Research online revealed no obvious statement upgrade for my particular case.

  I downloaded and installed v9.8 DAQmx as well as RealTime 2013 module on my development machine, and am trying to download the 4 GB device drivers.

  Is there a suggested method for the SMU-8101 software update / firmware must match that of my development machine that does not require me trying decrypt and download the packages manually?

  I've never worked with the SMU (or any remote system) with LabVIEW front and wait it would be an easy fix for someone more experienced in this.

  Owen

  AHA!

  OK, that explains it.  You actually have LabVIEW 2011 on target (SMU-8101) but you have LabVIEW 2013 on the host.  You have all the required software installed on the host computer, but there are conflicts between the required versions of the software on the controller itself compared to what you're trying to install now.  You have 3 ways to do this:

  (1) the cleaner to proceed is to keep track of all the software components that you have installed (version is not important) and then UNINSTALL all the controller software, and then REINSTALL your software (leaving MAX select the latest versions of everything).  This ensures that you'll get the latest components of software.

  (2) the 'simpler' wat to proceed is to pass by and "update" symbolizes all the components with an icon 'Bang' (yellow triangle with an exclamation point) to upgrade/reinstall the latest version found on the host - the icon of 'bang' software currently installed on the target, but more recent versions exist on the host computer.  Version does not update without user intervention, even if the other components require more recent versions.  This lump all your versions later, that's what want the latest version of DAQmx.

  (3) nuclear option - reformat your controller and reinstall all software.  This is not recommended, but this option always exists.

  -Danny

• Same code compiled for the cRIO-9074, but reports no diagram component calendar violation for cRIO-9067

  Hi, just got my new cRIO-9067. I have converted my project over the cRIO-9067 since the cRIO 9074. Same layout module, same engine, same scan code custom fpga, (hybrid mode).  I have no problem of compilation for the 9074, which is a lower performance FPGA architecting the 9067 FPGA.

  The final timetable for windows compilation shows that the timing is respected for all clocks - 40, 80 and 120 MHz (I use a clock derived for some code sctl). During the end of compilation, during the phase of gen bitfile, I get the dreaded time violation. Investigation of the breach indicates that it is not the custom code, it is not schema components. One of them seems to be linked to the card series OR 9870 I in the chassis.

  Why? Is there anything I can try with the compiler directives for this problem? You would think that it would be easier to compile for the highest performance FPGAS...

  OK, don't ask me how I thought this output - to run I changed nothing else than this: feed the I/O node a reference FPGA of e/s instead of configure the node via the menu "link to. It makes no sense, but the compilation succeeded when I did this.

  I know it is because I created a very simple test VI in my project and made sure it does not compile without it.

• Impossible to determine the application exit code

  Hi guys,.

  I used the code below at the exit of the application programmatically.

  Application:instance()->requestExit();

  but I get following errors:

  Impossible to determine the application exit code

  Please find the error attatched image.

  

  Please help me to fix it.

  Application::instance()->exit(0);
  

  Or any code you want to use instead of 0.

• Suddenly, my sound card does not work - try the devices and add/install the old hardware on the Assistant Manager, he finds ADSInstant HTV PC1, but sending the message... Impossible to install correctly the code 10

  tried the Device Manager and add/install the old hardware on the wizard... he finds ADSInstant HTV PC1, but sending the message... Impossible to install correctly the code 10

  Restore the system to then it was working properly.

• Impossible to compile the module vmnet only for VMware Player 4.0.3 build-703057 on Fedora x86_64 16

  During the update to VMware Player 4.0.3 I get this error for vmnet-only compilation. I found a patch for 4.0.2 and a similar compilation for the last error update 4.0.2 but not for version 4.0.3. Any tips?

  JOURNAL

  / usr/bin/make-j - C/tmp/vmware-root/modules/vmnet-only self-build SUPPORT_SMP = 1 HEADER_DIR=/lib/modules/3.3.2-6.fc16.x86_64/build/include CC = / usr/lib64/ccache/CCG GREP = / usr/bin/make IS_GCC_3 = no VMCCVER = 4.6.3 Using 2.6.x kernel build system. make: entering directory ' / tmp/vmware-root/modules/vmnet-only» do /lib/modules/3.3.2-6.fc16.x86_64/build/include/ - C... SUBDIRS = $PWD SRCROOT = $PWD. \ MODULEBUILDDIR = modules make [1]: Entering directory ' / usr/src/kernels/3.3.2-6.fc16.x86_64' CC [M] /tmp/vmware-root/modules/vmnet-only/userif.o CC [M] /tmp/vmware-root/modules/vmnet-only/netif.o CC [M] /tmp/vmware-root/modules/vmnet-only/filter.o ' / tmp/vmware-root/modules/vmnet-only/userif.c: in function ' VNetCsumCopyDatagram ': '. «/ tmp/vmware-root/modules/vmnet-only/userif.c:520:3: Fehler: Inkompatibler Typ as 1 Argument von "kmap «» «include/linux/highmem.h:48:61: Anmerkung: ' struct page * 'works, aber hat type Argument' const struct < anonymous > «» «/ tmp/vmware-root/modules/vmnet-only/userif.c:523:3: Fehler: Inkompatibler Typ as 1 Argument von "kunmap «» «include/linux/highmem.h:54:60: Anmerkung: ' struct page * 'works, aber hat type Argument' const struct < anonymous > «» make [2]: * [/ tmp/vmware-root/modules/vmnet-only/userif.o] Fehler 1 make [2]: * Warte auf noch nicht processes going... ' / tmp/vmware-root/modules/vmnet-only/filter.c:60:16: Fehler: "THIS_MODULE" ist yesterday nicht deklariert (nicht in einer Funktion). make [2]: * [/ tmp/vmware-root/modules/vmnet-only/filter.o] Fehler 1 ' / tmp/vmware-root/modules/vmnet-only/netif.c: in function ' VNetNetIfSetup ': '. ' / tmp/vmware-root/modules/vmnet-only/netif.c:134:7: Fehler: unbekanntes Feld "ndo_set_multicast_list"in the Initialisierung angegeben. /tmp/vmware-root/modules/vmnet-only/Netif.c:134:7: Warnung: Initialisierung von inkompatiblem Zeigertyp [standardmassig aktiviert] /tmp/vmware-root/modules/vmnet-only/Netif.c:134:7: Warnung: (nahe der Initialisierung as"vnetNetifOps.ndo_validate_addr '") [standardmassig aktiviert] make [2]: * [/ tmp/vmware-root/modules/vmnet-only/netif.o] Fehler 1 make [1]: * [_module_/tmp/vmware-root/modules/vmnet-only] error 2 make [1]: leaving directory ' / usr/src/kernels/3.3.2-6.fc16.x86_64' make: * [vmnet.ko] Fehler 2 make: leaving directory ' / tmp/vmware-root/modules/vmnet-only.

  1. Download this archive: http://weltall.heliohost.org/wordpress/wp-content/uploads/2012/01/vmware802fixlinux320.tar.gz
  2. Extract archive
  3. Edit the file patch - modules_3.2.0.sh.  Look for the line plreqver=4.0.2 and to takeplreqver=4.0.3
  4. Save the file, and then run it.sudo ./patch-modules_3.2.0.sh

  I have this picked up on the Internet and it worked for me, as I had the same problem after upgraging my Linux Distro.

  Caveat Emptor

  Thank you

  Sky

• Impossible to compile in 6i forms in the forms 11gAS (HP - Ux)

  We are compiling forms 6i shaped 11g (on HP - Ux server), we get an error.
  
  In all our forms 6i, we have classified under a group of objects. When we compile the forms in 11gAS we get an error
  
  "FRM-18108: unable to load the following items."
  
  The form in which is created the group object compiled successfully. But those forms which has classified this group object fails.
  
  The same mistake, we get to these forms of 6i where we have sub categorized library of objects.

  Your object library is in the forms_path that uses the compilation? The case of the file is the same?

• Impossible to compile the driver for windows in MDF

  I'm trying to use the windows driver instead of the Adobe driver by selecting the windows default printer 'use' in the target presentation window and recompiling, but apparently return to the target presentation printer Agent.

  I select the default windows printer and click ok:

  

  If I open immediately the objectives of the presentation, he shows that he did not save my selection because it always shows the selected Adobe presentation.

  

  Just in case it did, in fact, compile with the windows driver, I go ahead and compile to a new MDF and run jfmerge with the following command line:

  JFMerge mypo.mdf mypo.dat mypo.pcl - aiijfmerge.ini - zmypo.pcl - allmypo.log - auwpon - aspWindows

  This is what appears in the log:

  2009-11-04 12:13:30 jfmerge: [125] * processing data file: 'mypo.dat. '
  2009-11-04 12:13:30 jfmerge: [289] 'mypo.mdf' MDF file opens.
  2009-11-04 12:13:30 jfmerge: [247]'Windows' printer driver has not has been compiled in this MDF.
  2009-11-04 12:13:30 jfmerge: [210] nothing has been printed.

  Can someone do the light on how to get the Windows printer driver compiled in my mdf?

  Thanks in advance for any help!

  Phil

  Windows drivers and Agent print drivers are mutually exclusive.  In the design tool, under objective presentation select "Use print agent presentment target" and then select "clear all".  Then go back and select the windows drivers.

  see you soon

  c

• Remote access to SMU-8101

  Hello.

  I have a 1071-SMU-PXI chassis with controller SMU-8101 (Windows XP) and SMU-4496 module. Also, I NI DAQmx installed on the controller operating system and on another computer in the same network.

  Is it possible to acquire measurement data of this ADC on network computer using remote access? Or this feature is available only if you use real-time controllers?

  Thank you.

  When you perform a MXI installation like this, you essentially replace the embedded controller that installs in slot 1 with your laptop / desktop. You will need to install the driver daqmx for laptop/desktop computer computer which is connected to the chassis via MXI cable.

• Compilation of the variable results in LabVIEW FPGA

  Hello. I would ask why LabVIEW FPGA generates different results of compilation for the same code. When I compile several times my code, the maximum speed and total changes bitfile slices generated according to the compilation, but I does not alter with the FPGA VI. In addition, is the precise relationship of compilation? Thank you

  It's normal. The FPGA compiler starts to place pieces of code on the FPGA somewhat randomly and adjusts them until either the design adapts and responds to the criteria of the moment or there that the compiler determines that it cannot fit all the code and meet time constraints. The outputs that the FPGA VI generates when run will always be the same.

• XP shows the 0x80072EFD error code, I can ddownload on internet, but all of the updates fail

  I can download from the internet, but cannot update any programs at all, get code Error 0x80072EFD or 'impossible to connect to the server' messages on windows XP. having run "fix it." It fails not too

  Hello

  Method 1: the question it looks that the computer is not able to connect to the update server. Here is the article which allows to fix this problem.

  How to resolve problems connecting to Windows Update or Microsoft Update
  http://support.Microsoft.com/kb/818018/en-us

  Method 2; Temporary connection related errors may occur when you use Windows Update or Microsoft Update
  http://support.Microsoft.com/kb/836941

  Hope you will soon find your landline number.

• Application crashes after links compilations on the command line and running on Simulator

  Hi all

  I have a project where I need to link my static libraries built separately (but using the toolchain/compiler inside the BBNDK) for a sample application QML BB10.  I am relatively new to BB10 and its environment.

  Although the application compiles and links successfully, the performance of the application is segmenting online

  AbstractPane *root = qml->createRootObject();
  

  My other static libraries have many references to the C++ Standard Library, such as strings, streams etc. and these are inside libstdc++.a/.so. Also some references to struggling and Expat. And so I assured these library on my road to compile as follows

  qcc -Vgcc_ntox86 -lang-c++ -Wl,-rpath-link,/opt/bbndk/target_10_0_9_386/qnx6/x86/lib -Wl,-rpath-link,/opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib -o o-g/MyApp o-g/.obj/main.o o-g/.obj/MyApp.o o-g/.obj/moc_MyApp.o    -L/opt/bbndk/target_10_0_9_386/qnx6/x86/lib -L/opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib -L/opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/qt4/lib -L/opt/bbndk/lib ./myStaticLib.a /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/gcc/4.6.3/libstdc++.a /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libexpat.so.2 /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libsocket.so -lm -lbps -lbb -lbbcascades -lQtDeclarative -lQtScript -lQtSvg -lQtSql -lQtXmlPatterns -lQtXml -lQtGui -lQtNetwork -lQtCore
  

  With this application compiles / links with success but as said previously, it crashes inside createRootObject.

  If I don't specify my static library (myStaticLib.a), out of all references to myStaticLib.a in the code and remove the stdc library ++ application goes ahead and the screen correctly.

  NOTE: myStaticLib.a is not related to the QT code in any way. I call the method inside myStaticLib after that I booted properly QT and after showing the first screen in the code.

  I was able get out the base of the Simulator file and also use it with this gdb on my build machine. Here is the result of the BDG.

  root@server:/opt/bbndk#host_10_0_9_52/linux/x86/usr/bin/ntox86-gdb /home/puneet_narsapur/webrtc/ip/psl_p2pwebrtc_r2835_x86_bb10/trunk/third_party/libjingle/source/talk/examples/BBTalk/x86/o-g/PeerConnection /home/puneet_narsapur/webrtc/ip/psl_p2pwebrtc_r2835_x86_bb10/trunk/PeerConnection.core
  GNU gdb (GDB) 7.4 qnx (rev. 691)
  Copyright (C) 2012 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "--host=i686-pc-linux-gnu --target=i486-pc-nto-qnx6.5.0".
  For bug reporting instructions, please see:
  <http://www.gnu.org/software/gdb/bugs/>...
  Reading symbols from /home/puneet_narsapur/webrtc/ip/psl_p2pwebrtc_r2835_x86_bb10/trunk/third_party/libjingle/source/talk/examples/BBTalk/x86/o-g/PeerConnection...done.
  [New pid 8880242 tid 1]
  [New pid 8880242 tid 2]
  [New pid 8880242 tid 3]
  [New pid 8880242 tid 4]
  [New pid 8880242 tid 5]
  [New pid 8880242 tid 6]
  [New pid 8880242 tid 7]
  [New pid 8880242 tid 8]
  [New pid 8880242 tid 9]
  [New pid 8880242 tid 10]
  [New pid 8880242 tid 11]
  [New pid 8880242 tid 12]
  [New pid 8880242 tid 13]
  
  warning: Corrupted shared library list: 0x0 != 0x86f8000
  
  warning: Could not load shared library symbols for 15 libraries, e.g. libQtDeclarative.so.4.
  Use the "info sharedlibrary" command to see the complete listing.
  Do you need "set solib-search-path" or "set sysroot"?
  Program terminated with signal 11, Segmentation fault.
  #0  0xb086709e in __free () from /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libc.so.3
  Traceback (most recent call last):
    File "/opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libstdc++.so.6.0.16-gdb.py", line 59, in 
      from libstdcxx.v6.printers import register_libstdcxx_printers
  ImportError: No module named libstdcxx.v6.printers
  (gdb) bt
  #0  0xb086709e in __free () from /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libc.so.3
  #1  0xb0866c6b in free () from /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libc.so.3
  #2  0x08325e80 in operator delete(void*) ()
  #3  0x08325ecc in operator delete[](void*) ()
  #4  0x0832a69e in std::ios_base::~ios_base() ()
  #5  0xb962fa8f in ?? () from /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libbbcascades.so.1
  #6  0xb963074c in ?? () from /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libbbcascades.so.1
  #7  0xb952d3c8 in bb::cascades::AbstractTextControl::setText(QString const&) () from /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libbbcascades.so.1
  #8  0xb94df30c in bb::cascades::AbstractTextControl::qt_metacall(QMetaObject::Call, int, void**) () from /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libbbcascades.so.1
  #9  0xb94e7762 in bb::cascades::Label::qt_metacall(QMetaObject::Call, int, void**) () from /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libbbcascades.so.1
  #10 0xb9e9686d in ?? ()
  #11 0x089b6598 in ?? ()
  #12 0x00000002 in ?? ()
  #13 0x0000002f in ?? ()
  #14 0x07b9a14c in ?? ()
  Cannot access memory at address 0x89e24cc
  (gdb) info sharedlibrary
  warning: Corrupted shared library list: 0x0 != 0x86f8000
  From        To          Syms Read   Shared Object Library
  0xb8638000  0xb86500ac  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libexpat.so.2
  0xb82dd000  0xb8314824  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libsocket.so.3
  0xb8203000  0xb823b8d4  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libm.so.2
  0xb825f000  0xb82bf56c  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libbps.so.3
  0xb8450000  0xb848c780  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libbb.so.1
  0xb9400000  0xb9c5a200  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libbbcascades.so.1
                          No          libQtDeclarative.so.4
                          No          libQtScript.so.4
                          No          libQtSvg.so.4
                          No          libQtSql.so.4
                          No          libQtXmlPatterns.so.4
                          No          libQtXml.so.4
                          No          libQtGui.so.4
                          No          libQtNetwork.so.4
                          No          libQtCore.so.4
  0xb8665000  0xb86d7a88  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libcpp.so.4
  0xb0837000  0xb08d7cc0  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libc.so.3
  0xb8247000  0xb825c118  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libscreen.so.1
  0xb823c000  0xb824210c  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libpps.so.1
  0xb82c9000  0xb82cd0c4  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libslog2.so.1
  0xb8b44000  0xb8be11e4  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libbbsystem.so.1
  0xb82c2000  0xb82c7160  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libbbsystemlocale.so.1
  0xb82cf000  0xb82dabac  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libEGL.so.1
  0xb831d000  0xb832707c  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libGLESv2.so.1
  0xb8419000  0xb8425248  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libgestures.so.1
  0xb8436000  0xb844a1a0  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libimg.so.1
  0xb8aef000  0xb8b2447c  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libstrpattern.so.1
  0xbacf9000  0xbae94cd0  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libwebview.so.2
  0xb8427000  0xb842f48c  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/liblgmon.so.1
  0xb8493000  0xb84aa124  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libz.so.2
  0xb8ab4000  0xb8adf400  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libpng14.so.0
  0xb904c000  0xb912a0c0  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libiconv.so.1
  0xb8316000  0xb831b504  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libclipboard.so.1
  0xb84ab000  0xb84b2190  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libcontext.so.1
  0xb93a9000  0xb93d9774  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libnfc.so.1
  0xb8243000  0xb82460d0  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libnfc_bps.so.1
  0xbab17000  0xbacdcb74  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libicui18n.so.49
  0xbb800000  0xbd5c1258  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libwebkit.so.0
  0xbb01f000  0xbb498150  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libwebkitplatform.so.0
  0xbaeb5000  0xbb015644  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libicuuc.so.49
  0xbb56f000  0xbb6e57c0  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libgrskia.so.1
  0xb8629000  0xb8634280  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libimfclient.so.1
  0xb935c000  0xb939c26c  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libgoogleurl.so.0
  0xb8657000  0xb8663254  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libintl.so.1
  0xb9c6a000  0xb9cd99c8  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libcpp-ne.so.4
  0xb8430000  0xb8435128  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libcounters.so.1
  0xbe800000  0xbf952988  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libicudata.so.49
  0xbaa99000  0xbaaf5bec  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libcurl.so.2
  0xbb526000  0xbb557960  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libfontconfig.so.1
  0xbb4e6000  0xbb51c2b4  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libjpeg.so.4
  0xbb6fc000  0xbb78e4fc  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libsqlite3.so.1
  0xbda11000  0xbdb342dc  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libxml2.so.1
  0xbb4a1000  0xbb4db768  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libxslt.so.2
  0xbd6ae000  0xbd7273c8  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libfreetype.so.1
  0xbb79b000  0xbb7d14f8  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libharfbuzz.so.0
  0xb8a99000  0xb8aa8168  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libskia-qnx.so.0
  0xb8aab000  0xb8ab1120  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libppscache.so.1
  0xb8ae7000  0xb8aed150  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libmmrndclient.so.1
  0xb8ae0000  0xb8ae61bc  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libmd.so.1
  0xb848d000  0xb8492120  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libaoi.so.1
  0xbb7d5000  0xbb7fb7f4  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libinput_client.so.1
  0xbd628000  0xbd668138  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libhuapi.so.5
  0xb8b25000  0xb8b43838  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libcamapi.so.1
  0xbd5cf000  0xbd617450  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libiType.so.1
  0xbd8b1000  0xbd9179dc  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libWTLE.so.1
  0xbd81e000  0xbd883b50  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libinput_utilities.so.1
  0xb8be8000  0xb8bfa260  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libcares.so.1
  0xbd783000  0xbd7df6f8  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libssl.so.2
  0xbd670000  0xbd6aa5d8  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libgssapi.so.1
  0xb8328000  0xb832c084  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libstrm.so.1
  0xbd954000  0xbda060a4  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libsbgse56.so.0
  0xb93de000  0xb93eb1f4  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libmmedia.so.1
  0xb93ec000  0xb93fcaec  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libmmfilter.so.1
  0xb9c5b000  0xb9c68d00  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libbz2.so.1
  0xb939e000  0xb93a626c  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libhiddi.so.1
  0xbdd07000  0xbdeb7764  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libcrypto.so.2
  0xb9ce8000  0xb9cf13ec  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libnbutil.so.1
  0xbdc23000  0xbdc98498  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libkrb5.so.1
  0xb9cde000  0xb9ce6310  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libheimntlm.so.1
  0xbdb37000  0xbdbca0e8  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libasn1.so.1
  0xb8200000  0xb8202110  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libcom_err.so.1
  0xbd736000  0xbd77c91c  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libhx509.so.1
  0xbaa7f000  0xbaa8f5f0  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libroken.so.1
  0xbd7ec000  0xbd8140fc  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libwind.so.1
  0xb8414000  0xb84185c0  Yes (*)     /opt/bbndk/target_10_0_9_386/qnx6/x86/usr/lib/libheimbase.so.1
                          No          libHwEGL.so
                          No          libegl_gallium.so
                          No          libHwglapi.so
                          No          libpipe_vmwgfx_drv.so
  0xbdf18000  0xbe00a9b8  Yes         /opt/bbndk/target_10_0_9_386/qnx6/x86/lib/libstdc++.so.6
                          No          libllvmpipe_drv.so
                          No          libHwGLESv2.so
  (*): Shared library is missing debugging information.
  (gdb) q
  root@server:/opt/bbndk#
  

  It seems to be crashing within libc.so while trying to release something. There is not any change in the QML code at all.

  Even if everything seems to be compilations and links correctly, I'm not able to find the reason for this accident.

  I don't change all code QML, but if I include my library and stdc ++ it crashes. If I don't get my library and stdc ++ he does not crash and all is well.

  Can someone help me please how to debug this problem? Stuck in this during more than two days

  Found the problem. For the other library that I was building with the BB10 NDK build tools, I was not using "qcc-Vgcc_ntox86-lang-c ++. I used instead of the ntox86-g ++ under the host directory. And it lacked the required compiler flags that were used internally by qcc.

  After changing the compiler, application has compiled, I did not provide libstdc ++ .a for him also, as well as the application has been properly executed well.