CVI fail to compile in release mode

I am getting linker errors when I attempt to compile or build a project in the Release mode. In Debug mode the compile and build works fine. Any ideas?
Dell E6410
OS = XP
not using Release64 or Debug64 yet...
ChipB
Solved!
Go to Solution.
Attachments:
snap.jpg ‏27 KB

Some Opperator error... Fixed but not sure what caused it.
Cheers!
ChipB

Similar Messages

  • Code runs fine in debug mode but hangs when compiled in release mode

    I am struggling with the following problem. I have code which runs fine when it is executed in debug mode. However, when I compile it in release mode and run the executable, the code freezes and does not work. The code acquires images from a Hamamatsu camera. In the debug mode I am able to continuously acquire images. However, in the release version, the code hangs after acquiring the first image.
    I am using LabWindows/CVI version 7.
    I would greatly appreciate if I can get any help/suggestions in resolving this problem?
    Thanks!
    Regards,
    Sripad
    Solved!
    Go to Solution.

    Sripad:
    If you search this forum for "debug release crash" or "release version crash" or similar phrases, you'll find that this is a pretty common question.  Look through the other posts you find here to see if anything is applicable to you.
    The debug version does some things like padding variables so you can sometimes overrun your declared variable space without overwriting the next variable.  In the release, the variables are packed, so if you overrun one, you are overwriting another.  Just one possible difference.
    You can do some things in your release code to see where things get lost, like (temporarily using printf statements after multiple statements at the start and end of your loop to try to identify that failing line of code.
    Look through other threads to find other ideas.

  • Obj-C errors in a C   app in release mode

    I've made this c++ app that uses GLUT and OpenGL to display a square on the screen that you can move around with the arrow keys. I wanted to show my friend, so I compiled in release mode. Upon doing so, I got 1120 errors in various Obj-c headers that I don't import. I've never seen them before, and I'm pretty sure GLUT doesn't use them because I can compile in debug mode and have the app work just fine.
    Source code is here: http://dl.dropbox.com/u/2223161/OpenGL.zip
    Does anyone know why that's happening?

    While in Release build double click on the OpenGL target to get the Target Info panel.  Go to the Build tab, make sure the config is set to 'Release' and scroll down to the GCC Language section and remove '$(SYSTEM_LIBRARY_DIR)/Frameworks/AppKit.framework/Headers/AppKit.h' from the 'Prefix Header' setting leaving it blank. Rebuild.

  • Event receiver works perfectly in debug mode, but fails in release mode

    Here is my item added event which works perfectly and gives read permission to CCfield user in debug mode, but doesn't give permissions to CCfield user when item added event is triggered in release mode:
    base.ItemAdded(properties);
    try
    SPListItem item = properties.ListItem;
    string idnumber = Convert.ToString(properties.ListItem["ID"]);
    string itemurl = properties.ListItem.Url;
    SPWeb web = properties.Web;
    item.BreakRoleInheritance(false, false);
    //item.Update();
    string ccfield = Convert.ToString(properties.ListItem["EmailCc"]);
    string STRFirst = "<" ;
    string STRLast = ">";
    int Pos1 = ccfield.IndexOf(STRFirst) + STRFirst.Length;
    int Pos2 = ccfield.IndexOf(STRLast);
    string ccfield1 = ccfield.Substring(Pos1, Pos2 - Pos1);
    SPUser user = item.Web.EnsureUser(ccfield1);
    SPRoleAssignment roleAssignment = new SPRoleAssignment(user);
    roleAssignment.RoleDefinitionBindings.Add(web.RoleDefinitions["Read"]);
    item.RoleAssignments.Add(roleAssignment);
    catch (Exception e)
    throw;
    Any help?
    sk.Rakhishma

    Event receivers run using the permissions of the user who triggered the event. If your user does not have rights to manage permissions then you will need to run your security code with elevated permisisons.
    SPSecurity.RunWithElevatedPrivileges(delegate()
    { your code here } )
    Note that RunWithElevatedPermissions will not work with Sandbox code.
    Mike Smith TechTrainingNotes.blogspot.com
    my SP customization book

  • Sun C 5.9 Build13_0 2006/01/06 fails to compile wchar.h

    On both IA-32 and AMD64 systems running Red Hat Enterprise Linux AS release 4 (Nahant Update 1), c89 fails to compile
    a single-line file containing
    #include <wchar.h>
    c89 -c foo.c
    "/usr/include/wchar.h", line 508: long long not allowed in Xc mode
    "/usr/include/wchar.h", line 508: invalid type combination
    "/usr/include/wchar.h", line 515: long long not allowed in Xc mode
    "/usr/include/wchar.h", line 515: invalid type combination
    This header file requires support of long long, so the
    restriction in the Xc mode should probably be relaxed
    for these platforms, since we cannot change system
    header files.

    Ah, I see the c89 script on RedHat has a bug, i.e.
    it fails to add -pedantic. So it could properly diagnose
    the use of long long ...
    % more t.c
    long long i;
    % /usr/bin/c89 t.c -c
    % /usr/bin/c89 t.c -c -pedantic
    t.c:1: warning: ISO C90 does not support `long long'
    % cat /usr/bin/c89
    #!/bin/sh
    fl="-std=c89"
    for opt; do
      case "$opt" in
        -ansi|-std=c89|-std=iso9899:1990) fl="";;
        -std=*) echo "`basename $0` called with non ANSI/ISO C option $opt" >&2
                exit 1;;
      esac
    done
    exec /usr/bin/gcc $fl ${1+"$@"}
    %

  • Sun C 5.9 Build13_0 2006/01/06 fails to compile c stdint.h on IA-32

    On GNU/LInux on IA-32 (Red Hat Enterprise Linux AS release 4 (Nahant Update 1)), c89 fails to compile a single-line test
    file with the line
    #include <stdint.h>
    "/usr/include/stdint.h", line 44: long long not allowed in Xc mode
    "/usr/include/stdint.h", line 44: invalid type combination
    "/usr/include/stdint.h", line 59: long long not allowed in Xc mode
    "/usr/include/stdint.h", line 59: invalid type combination
    "/usr/include/stdint.h", line 73: long long not allowed in Xc mode
    "/usr/include/stdint.h", line 73: invalid type combination
    "/usr/include/stdint.h", line 84: long long not allowed in Xc mode
    "/usr/include/stdint.h", line 84: invalid type combination
    "/usr/include/stdint.h", line 100: long long not allowed in Xc mode
    "/usr/include/stdint.h", line 100: invalid type combination
    "/usr/include/stdint.h", line 113: long long not allowed in Xc mode
    "/usr/include/stdint.h", line 113: invalid type combination
    "/usr/include/stdint.h", line 139: long long not allowed in Xc mode
    "/usr/include/stdint.h", line 139: invalid type combination
    "/usr/include/stdint.h", line 141: long long not allowed in Xc mode
    "/usr/include/stdint.h", line 141: invalid type combination
    On this platform, long long support is essential; we cannot
    change system header files. I suggest that the restriction
    in -Xc mode on long long be relaxed for this platform.

    Well, its the task of -Xc to enforce strict conformance (that is prohibit compilation of nonstandard and thus nonportable code).
    I believe you know that long long is not a standard integer type in C90.
    If you need -Xc you may conisder compiling with c99.
    If you definitely need c90 then you better skip -Xc and compile with "cc -Xa -xc99=%none".
    We will consider relaxing -Xc on linux, though it does not strike me as a most elegant solution ...
    regards,
    Fedor.

  • Sun C 5.9 Build13_0 2006/01/06 fails to compile stdlib.h

    On both IA-32 and AMD64, c89 fails to compile a single-line
    test file containing
    #include <stdlib.h>
    "/usr/include/stdlib.h", line 537: long long not allowed in Xc mode
    "/usr/include/stdlib.h", line 537: invalid type combination
    I suggest that the "no long long" in Xc mode be dropped
    on these platforms, because that type is used in standard
    header files needed by most software.

    We will consider turning this into a warning and supressing that warning in system header files.

  • Java.lang.RuntimeException: failed to compile execlets (JAVA embeding issue in BPEL 2.0)

    HI i was trying to use java code in BPEL 2.0 by using java Embedding. while deploying the application getting the error.
    even after importing the corrsponding class
    below is the code snippet for the same :
    <import location="oracle.soa.management.facade.Locator"
         importType="http://schemas.oracle.com/bpel/extension/java"/>
         <import location="oracle.soa.management.facade.LocatorFactory"
         importType="http://schemas.oracle.com/bpel/extension/java"/>
         <import location="oracle.soa.management.facade.Component"
         importType="http://schemas.oracle.com/bpel/extension/java"/>
    <extensionActivity>
          <bpelx:exec name="Java_Embedding1" language="java">
            <![CDATA[Locator locator = LocatorFactory.createLocator();    
    String compositeRevision = (String)getVariableData("compositeRevision");  
    String compositeNameRevision = "ASG/ImportCustomerData!"+ compositeRevision; 
    Composite prowessCustomerComposite = (Composite)locator.lookupComposite(compositeNameRevision);   
    CompositeInstanceFilter filter = new CompositeInstanceFilter();    
    filter.setState(CompositeInstance.STATE_RUNNING);]]>
          </bpelx:exec>
        </extensionActivity>
    while deploying gettting below error.
    06:18:58 PM] Error deploying archive sca_ImportCutomerData_rev1.0.jar to partition "default" on server AdminServer [http://LTRTHIPIREDDY.keste.com:7001]
    [06:18:58 PM] HTTP error code returned [500]
    [06:18:58 PM] Error message from server:
    There was an error deploying the composite on AdminServer: Deployment Failed: Error occurred during deployment of component: importCustomerData_BPEL to service engine: implementation.bpel, for composite: ImportCutomerData: ORABPEL-05250
    Error deploying BPEL suitcase.
    error while attempting to deploy the BPEL component file "E:\Oracle\Middleware\user_projects\domains\Raja_domain\servers\AdminServer\dc\soa_3ca99378-812f-460f-9760-d19a15c0ef44"; the exception reported is: java.lang.RuntimeException: failed to compile execlets of importCustomerData_BPEL
    This error contained an exception thrown by the underlying deployment module.
    Verify the exception trace in the log (with logging level set to debug mode).
    [06:18:58 PM] Check server log for more details.
    [06:18:58 PM] Error deploying archive sca_ImportCutomerData_rev1.0.jar to partition "default" on server AdminServer [http://LTRTHIPIREDDY.keste.com:7001]
    [06:18:58 PM] ####  Deployment incomplete.  ####
    [06:18:58 PM] Error deploying archive file:/C:/JDeveloper/mywork_Arbonne/CustomerInboundApp/ImportCutomerData/deploy/sca_ImportCutomerData_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    Thanks in Advance...
    rajashekar

    Hi have solved the issue by importing the  class file.
    <import location="oracle.soa.management.facade.Locator"
              importType="http://schemas.oracle.com/bpel/extension/java"/>
      <import location="oracle.soa.management.facade.LocatorFactory"
              importType="http://schemas.oracle.com/bpel/extension/java"/>
      <import location="oracle.soa.management.facade.Composite"
              importType="http://schemas.oracle.com/bpel/extension/java"/>
      <import location="java.util.List"
              importType="http://schemas.oracle.com/bpel/extension/java"/>
      <import location="oracle.soa.management.util.CompositeInstanceFilter"
              importType="http://schemas.oracle.com/bpel/extension/java"/>
      <import location="oracle.soa.management.facade.CompositeInstance"
              importType="http://schemas.oracle.com/bpel/extension/java"/>

  • Using Zllib, Xerces and Boost (in release mode)

    I've developped a Export plugin which used Zlib, Xerces, and Boost libs. (This libs are used in a statically.)
    In debug mode, the plugin is loaded correctly, and worked fine.
    I want to build this plugin in a release mode, in order to test it on an designer's workstation.
    The compilation is executed without problems. the same for link operations. But when I tried to load at Illustrator's startup, a message box is shown, telling me my plugin was not loaded correctly, and not loaded at all.
    I've took a look at my project settings, to check if my settings were ok (used static libs in debug or release mode), if there was no conflicts in precompiled header............
    I did not find! So if someone would have some tips to help me, it would be great!
    Thx,
    Thomas.

    I have finally found the problem!
    After having unplugged all the code I have written and replugged the all by block of code,
    I have found where I was wrong! it has taken me almost a day of work!
    the probleme was in the using of #ifndef, define!
    just this few lines:
    #ifndef _XERCESSTRING_H
    #define _XERCESSTRING_H
    #include <xercesc/util/XMLString.hpp>
    #ifdef XERCES_CPP_NAMESPACE_USE
    XERCES_CPP_NAMESPACE_USE
    #endif
    I have fixed that! now project can be built in release.
    Thanks for helping me!
    thomas.

  • LMMS fails to compile

    As the topic title says, LMMS fails to compile from AUR. Here's the output...
    Making all in plugins
    make[2]: Entering directory `/var/abs/local/lmms/src/lmms-0.2.1/plugins'
    Making all in audio_file_processor
    make[3]: Entering directory `/var/abs/local/lmms/src/lmms-0.2.1/plugins/audio_file_processor'
    make all-am
    make[4]: Entering directory `/var/abs/local/lmms/src/lmms-0.2.1/plugins/audio_file_processor'
    if /bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../src/lib -I. -I/opt/qt4/include/Qt -I/opt/qt4/include -D_REENTRANT -DQT_THREAD_SUPPORT -DPLUGIN_NAME="audiofileprocessor" -g -O2 -floop-optimize2 -fgcse-sm -fgcse-las -ftree-vectorize -ftree-loop-linear -funsafe-loop-optimizations -Wunsafe-loop-optimizations -DSINGLE_SOURCE_COMPILE -ansi -Wall -fno-exceptions -I/usr/local/include -MT audio_file_processor.lo -MD -MP -MF ".deps/audio_file_processor.Tpo" -c -o audio_file_processor.lo audio_file_processor.cpp; \
    then mv -f ".deps/audio_file_processor.Tpo" ".deps/audio_file_processor.Plo"; else rm -f ".deps/audio_file_processor.Tpo"; exit 1; fi
    g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../src/lib -I. -I/opt/qt4/include/Qt -I/opt/qt4/include -D_REENTRANT -DQT_THREAD_SUPPORT -DPLUGIN_NAME=audiofileprocessor -g -O2 -floop-optimize2 -fgcse-sm -fgcse-las -ftree-vectorize -ftree-loop-linear -funsafe-loop-optimizations -Wunsafe-loop-optimizations -DSINGLE_SOURCE_COMPILE -ansi -Wall -fno-exceptions -I/usr/local/include -MT audio_file_processor.lo -MD -MP -MF .deps/audio_file_processor.Tpo -c audio_file_processor.cpp -fPIC -DPIC -o .libs/audio_file_processor.o
    ../../include/track.h:511: error: ISO C++ forbids declaration of 'QPtrList' with no type
    ../../include/track.h:511: error: expected ';' before '<' token
    make[4]: *** [audio_file_processor.lo] Error 1
    make[4]: Leaving directory `/var/abs/local/lmms/src/lmms-0.2.1/plugins/audio_file_processor'
    make[3]: *** [all] Error 2
    make[3]: Leaving directory `/var/abs/local/lmms/src/lmms-0.2.1/plugins/audio_file_processor'
    make[2]: *** [all-recursive] Error 1
    make[2]: Leaving directory `/var/abs/local/lmms/src/lmms-0.2.1/plugins'
    make[1]: *** [all-recursive] Error 1
    make[1]: Leaving directory `/var/abs/local/lmms/src/lmms-0.2.1'
    make: *** [all] Error 2
    ==> ERROR: Build Failed. Aborting...
    You may also want to know that I'm using the non-cvs version of LMMS from AUR, and I am running 64-bit Arch.

    Susu wrote:make[1]: Entering directory `/tmp/yaourt-tmp-sushi/aur-lmms/lmms/src/lmms-0.2.1'
    Making all in buildtools
    make[2]: Entering directory `/tmp/yaourt-tmp-sushi/aur-lmms/lmms/src/lmms-0.2.1/buildtools'
    if g++ -DHAVE_CONFIG_H -I. -I. -I.. -march=i686 -O2 -pipe -floop-optimize2 -fgcse-sm -fgcse-las -ftree-vectorize -ftree-loop-linear -funsafe-loop-optimizations -Wunsafe-loop-optimizations -DSINGLE_SOURCE_COMPILE -ansi -Wall -fno-exceptions -I/usr/local/include -MT bin2res.o -MD -MP -MF ".deps/bin2res.Tpo" -c -o bin2res.o bin2res.cpp; \
    then mv -f ".deps/bin2res.Tpo" ".deps/bin2res.Po"; else rm -f ".deps/bin2res.Tpo"; exit 1; fi
    [b]cc1plus: error: unrecognized command line option "-floop-optimize2"[/b]
    make[2]: *** [bin2res.o] Error 1
    make[2]: Leaving directory `/tmp/yaourt-tmp-sushi/aur-lmms/lmms/src/lmms-0.2.1/buildtools'
    make[1]: *** [all-recursive] Error 1
    make[1]: Leaving directory `/tmp/yaourt-tmp-sushi/aur-lmms/lmms/src/lmms-0.2.1'
    make: *** [all] Error 2
    ==> ERROR: Build Failed. Aborting...
    Error: Makepkg was unable to build lmms package.
    Remove the -floop-optimize2 switch from the compile lines. If it can't be done with a configure option, patch the Makefiles. You can use sed:
    sed -i 's/-floop-optimize2//g' path/to/Makefile
    Do that to all Makefiles.

  • Thread won't run in release mode

    My application runs fine in Debug mode. I have several threads. A couple just blink some LEDS. In release mode they don't blink and my main function that is triggered by a button which runs a callback function that launches another thread doesn't work. 

    Hello,
    it's difficult to try guessing what's happening with no informations available. Apparently ther's something that's causing a program crash in release mode and you suppose it relates to some problem in memory allocation. Additionally, it seems your program is consuming system resources until it fills up all available memory.
    Are you freeing the dynamic memory when no longer needed? Are you sure you don't have any memory leak that can cause this increment in memory occupation? You must double check that every dynamic array allocated is freed when no longer used; you may want to swap part of the dynamic memory to disk if you are not using it constantly.
    Additionally, have you a consistent and robust error checking method that logs all errors found to the user interface or to disk?
    Another hint if you have CVI2009+ can be to activate extended debugging level in Build Options, next run the program some time in debug mode and close it: if some resources are not properly freed the Resource tracking window should appear with all allocated resources listed that are not correctly freed by the code.
    Proud to use LW/CVI from 3.1 on.
    My contributions to the Developer Zone Community
    If I have helped you, why not giving me a kudos?

  • Assembly (via xaml/xmlns) not found- but only in release mode and running as ActiveX

    Hi there,
    strange probleme here:
    I have an Active-X. That Active-X uses the ElementHost to display a WPF UserControl.
    The WPF UserControl references a few other Assemblies.
    One of those referenced Assemblies implements BitmapEffects using Pixel Shaders. (bar.dll)
    Here is a sample:
    <UserControlx:Class="MyNamespace.MyControls.MyControl"
    xmlns:foo="clr-namespace:Foo;assembly=Foo"
    xmlns:bar="clr-namespace:Bar;assembly=Bar"
    >
    <Grid>
      <foo:MyElement
    /> 
    => no Problem
      <Image>
        <Image.Effect>
          <bar:CombinedEffects 
    => Exception: bar.dll not found 
             Brightness="{Binding...     
             Contrast="{Binding...}"
    />
        </Image.Effect>
      </Image>
    </Grid>
    It works when i use a Demo-App which shows the Active-X on a WinForm. (Debug and release)
    It works also when i register the debug version - the activex is shown in IE.
    But the release version of ActiveX is failed to load in IE: because bar.dll is not found.
    Note: no Problems with foo.dll !
    I put the following lines in the constructor to force bar.dll is loaded before InitializeComponents():
    stringcodeBase = System.Reflection.Assembly.GetExecutingAssembly().CodeBase;
    UriBuilderuri =
    newUriBuilder(codeBase);
    stringpath =
    Uri.UnescapeDataString(uri.Path);
    stringfullpath = System.IO.Path.Combine(System.IO.Path.GetDirectoryName(path),
    "bar.dll");
    AppDomain.CurrentDomain.Load(System.Reflection.AssemblyName.GetAssemblyName(fullpath));
    Surprise: Now it works also in release mode.
    This behaviour looks strange to me.
    Is there any known bug within WPF and loading assemblies defined in xmlns uri?
    Known Problems of Using WPF+ElementHost in ActiveX?
    Known issues with PixelShaders+ActiveX / DirectX + ActiveX?
    Thanks

    Hi Businesskasper,
    >>It works also when i register the debug version - the activex is shown in IE.
    >>But the release version of ActiveX is failed to load in IE: because bar.dll is not found.
    The Internet Explorer Extension Development is a better place for IE extension development questions. I’ve moved it there for you.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • VMPlayer 3.1.5: Failed to compile module vmmon

    Hi,
    yesterday I updated VMPlayer but after that it doesn't work. When I try to start the program it advice me that 'Before you can run VMware, several modules must be compiled and loaded into the running kernel'. I select the 'Install' button but the procedure fails immediately during the compiling of the 'Virtual Machine Monitor'.
    The problem seems to be the vmmon module.
    Oct 10 10:49:57.775: app-3076052672| Log for VMware Workstation pid=1942 version=7.1.5 build=build-491717 option=Release
    Oct 10 10:49:57.775: app-3076052672| The process is 32-bit.
    Oct 10 10:49:57.775: app-3076052672| Host codepage=UTF-8 encoding=UTF-8
    Oct 10 10:49:57.775: app-3076052672| Logging to /tmp/vmware-root/setup-1942.log
    Oct 10 10:49:58.133: app-3076052672| modconf query interface initialized
    Oct 10 10:49:58.134: app-3076052672| modconf library initialized
    Oct 10 10:49:58.218: app-3076052672| Your GCC version: 4.6
    Oct 10 10:49:58.226: app-3076052672| Your GCC version: 4.6
    Oct 10 10:49:58.248: app-3076052672| Your GCC version: 4.6
    Oct 10 10:49:58.276: app-3076052672| Your GCC version: 4.6
    Oct 10 10:49:58.297: app-3076052672| Your GCC version: 4.6
    Oct 10 10:49:58.394: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.402: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.410: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.419: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.427: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.496: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.505: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.513: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.521: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.530: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.536: app-3076052672| Your GCC version: 4.6
    Oct 10 10:49:58.558: app-3076052672| Your GCC version: 4.6
    Oct 10 10:49:58.652: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.660: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.668: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.676: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.685: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.690: app-3076052672| Your GCC version: 4.6
    Oct 10 10:49:58.712: app-3076052672| Your GCC version: 4.6
    Oct 10 10:49:58.878: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.887: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.896: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.905: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:58.913: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:59.512: app-3076052672| Trying to find a suitable PBM set for kernel 3.0-ARCH.
    Oct 10 10:49:59.513: app-3076052672| Building module vmmon.
    Oct 10 10:49:59.525: app-3076052672| Extracting the sources of the vmmon module.
    Oct 10 10:49:59.582: app-3076052672| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmmon-only auto-$
    Oct 10 10:50:05.007: app-3076052672| Failed to compile module vmmon!
    I try to compile the modules with the command vmware-modconfig --console --install-all but it returns me:
    $ sudo vmware-modconfig --console --install-all
    Password:
    Stopping VMware services:
    VMware USB Arbitrator done
    VM communication interface socket family done
    Virtual machine communication interface done
    Virtual machine monitor done
    Blocking file system done
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
    make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
    CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
    /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:47:44: error: ‘SPIN_LOCK_UNLOCKED’ undeclared here (not in a function)
    /tmp/vmware-root/modules/vmmon-only/linux/iommu.c: In function ‘IOMMU_SetupMMU’:
    /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:103:28: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
    /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:113:17: warning: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘long long unsigned int’ [-Wformat]
    /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:117:35: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
    /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:120:20: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64’ [-Wformat]
    make[2]: *** [/tmp/vmware-root/modules/vmmon-only/linux/iommu.o] Error 1
    make[1]: *** [_module_/tmp/vmware-root/modules/vmmon-only] Error 2
    make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
    make: *** [vmmon.ko] Error 2
    make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
    Unable to install vmmon

    I am Gianluca wrote:It works!
    Thank you very much BxS
    I use VMware for a long time, it normally needs patchs for new kernels, Workstation 8 and Player 4 for now don't need any, they simple work out of the box, very nice

  • Performance Diference between debug mode and release mode

    Hi ,
    I have been running an C++ multithreaded application with below technical specification on Production for more than an year.
    OS - Solaris 10 , Opteron
    Compiler - Sun Studio 11
    Bit Mode - 64
    I wanted to know what is the difference in the debug mode of an C++ application compiled with -g option and a release mode compiled with an optimization apart from the size of the binary and availability of debug information in case of a crash.
    1) Does it degrade the performance of the application? If yes by what extent?
    2) Does it use more memory?
    3) Will switching from Debug to Release mode with some optimization coupled with any kind of risk like byte guard etc which could lead to dumps and all? If yes what could those be?
    4) Which optimization level should be used?
    Regards,
    Ankur Verma

    If you compile without any optimization (with or without -g), you will see a noticeable difference in performance in most programs compared to compiling with a reasonable level of optimization. How much difference depends on the nature of the program, and what percentage of time is spent in code regions that can benefit from the code improvements.
    If you add -g, function inlining is disabled, which can dramatically reduce program performance. You can't debug a function that is generated inline, which is why this option disables inlining. (The +d option also disables inlining.)
    If you use -g0 instead of -g, function inlining is preserved.
    If you use -g0 with optimization, you get the advantages of optimization while still allowing limited debugging. (Local variables are not visible.) Beginning with Sun Studio 12 update 1, the current release, -g with optimization enables function inlining, so the effect of (for example) "-O -g" becomes the same as "-O -g0".
    A few optimizations are disabled with -g or -g0, the exact difference depending on the compiler release and patch level. Most programs won't see a difference in performance.
    Since you are running on Solaris 10, you should upgrade to the current release, Sun Studio 12 update 1. You will get many improvements and some new diagnostic tools. The new release is a drop-in replacement for Studio 11. You don't have to recompile any existing binaries, but you will want to recompile to get improved performance.
    [http://developers.sun.com/sunstudio/]

  • Hyperlink to a zip file fails during compile

    RoboHTML v.5.0.3
    Windows XP, Office 2007
    In my help file I create a hyperlink to a *.zip file (128MB) that is located on my C drive.
    The Zip appears in my baggage files.
    The Zip file contains an .exe and .msi file.
    Everything compiles when creating the chm except the zip file.
    Media Manager Demo 3.0.0.5.zip
    HHC5001: Error:
    Media Manager Demo 3.0.0.5.zip :
    An error occurred while reading "c:\Program Files\RoboHelp Office\RoboHTML\ESI Demo Kit\!SSL!\Microsoft_HTML_Help\!chm_tmp_folder_0\Media Manager Demo 3.0.0.5.zip".
    HHC5003: Error:
    Media Manager Demo 3.0.0.5.zip :
    Compilation failed while compiling Media Manager Demo 3.0.0.5.zip.
    The following files were not compiled:
    Media Manager Demo 3.0.0.5.zip
    I've searched for info on this topic but can't find any. Is it possible to create a hyperlink to a Zip file?
    Any help is appreciated.

    Hi there
    Colum may be spot on, but in case that isn't quite it, you may wish to change the file name so that instead of this:
    Media Manager Demo 3.0.0.5.zip
    It's something like this:
    Media_Manager_Demo_3_0_0_5.zip
    Note that each space now has an underscore as well as each of the dots having underscores.
    Cheers... Rick
    Helpful and Handy Links
    RoboHelp Wish Form/Bug Reporting Form
    Begin learning RoboHelp HTML 7 or 8 within the day - $24.95!
    Adobe Certified RoboHelp HTML Training
    SorcerStone Blog
    RoboHelp eBooks

Maybe you are looking for