CVI 2010 SP1 Crash

Hallo,
ich habe ein Update von CVI 2009 auf CVI 2010 durchgeführt und habe jetzt ein Problem.
Eine meiner Applikationen lässt sich nicht mehr im Debugmodus starten,
Noch vor dem Eintritt in die main()-Routine stürtzt die Applikation ab (siehe Screenshot im Anhang).
Im Releasemodus läuft alles normal.
Danke für Ihre Hilfe im vorraus.
MFG,
Christoph Pierednik.
Solved!
Go to Solution.

In the past I had the same problem and thanks to NI support I solved it.
As explained here I had to remove some of the listed import library I had previously included.
As a matter of fact in the document I linked there is
The base version of LabWindows/CVI includes these import libraries, and LabWindows/CVI automatically loads these libraries when it starts up and searches them to resolve references at link time. Thus, you do not have to include these libraries in your project.
Vix
In claris non fit interpretatio
Using LV 2013 SP1 on Win 7 64bit
Using LV 8.2.1 on WinXP SP3
Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

Similar Messages

  • Announcement: LabWindows/CVI 2010 SP1 Run-Time Engine Updated

    A new version of the LabWindows/CVI 2010 SP1 Run-Time Engine (10.0.1.434) is now available for download. The new version includes Security Update 5Q5FJ4QW which resolves security vulnerabilities in components installed with LabWindows/CVI 2010 SP1 and earlier and LabVIEW 2011 and earlier. Further details can be found at KnowledgeBase Article 5Q5FJ4QW: How Does National Instruments Security Update 5Q5FJ4QW Affect Me? Installing the security update will have the same effect as installing the new version of the Run-Time Engine.
    The update can be downloaded from the Drivers and Updates page. The LabWindows/CVIRun-Time Engine is a free download.
    National Instruments
    Product Support Engineer

    The correct link should be this one
    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?

  • Labwindows cvi 2010 sp1 Device drivers

    Hi all
      I am trying to install cvi 2010 sp1 and it is asking for the Device Drivers for the program, where can I find the drivers for the sp1.
    To finish installing
    I have some older drivers but what is the latest for sp1
    Thanks in advance

    Hi Iriddick,
    You can choose to not install the Device Drivers with CVI and you will not get that window.  You can also cancel installing the Device Drivers without cancelling the CVI installation.  If you would like to install the Device Drivers, you can find the latest version by searching for "device drivers" at the ni.com main page.  The current latest version is the NI Device Drivers 2011.08.
    Regards,
    Brandon V.
    Applications Engineering
    National Instruments
    www.ni.com/support

  • Does the CVI 2010 SP1 download link work?

    The file downloaded from the SP1 link seems to be the non serviced pack version. After the "install" which proceeded way too quickly, the Help >>About still shows LW/CVI 2010 Version 10.0.0(360). Am I missing something or am I just too early?
    Solved!
    Go to Solution.

    Wolfgang - you just beat me to it   They should be updated now.
    blakney - Service Pack updates will only be available through Update Service 2.0, and they will actually not be available through Update Service 2.0 for another month or so.  There are some issues we're still trying to work out to make sure the Update Service experience is good for everyone.
    NickB
    National Instruments

  • CVI 2010 compiler crash

    This short piece of code below causes compiler crash in CVI 2010 - in CVI9.0 it works fine.
    Thanks for help.
    jirjan
    /* Compiler Crash example, CVI 2010 - v10.0.0 */
    static void fctDummy1(void) {};
    static void fctDummy2(void) {};
    typedef struct tagMyStruct
      void (*DummyFunction1)  ( void );
      void (*DummyFunction2)  ( void );
    } tMyStruct;
             tMyStruct MyFctStruct         = {fctDummy1, fctDummy2};
    const tMyStruct MyConstFctStruct = {fctDummy1, fctDummy2};
    void MyTest(void)
       MyFctStruct.DummyFunction1();
       MyFctStruct.DummyFunction2();
       /* this line doesn't cause the compiler crash...!!*/
       MyConstFctStruct.DummyFunction1();
       /* BUT next line caused the compiler crash...!!*/
       MyConstFctStruct.DummyFunction2();

    It is a very simple project with one source file only - sending in attachment (adapt to your project path or create simple project with .c file)..As I wrote before - with CVI9.0 (and/or any C compiler) I can compile the source file, CVI 2010 crashes while compiling..
    Thanks for your time
    Jiri
    Attachments:
    CompilerTest.zip ‏3 KB

  • CVI 2010 SP1 Graph Control Resizing Following Panel Resizing Bug

    Steps to duplicate:
    - In a running application, compress a panel containing a graph control with a top x-axis down to some very small size.
    - Re-expand the panel.
    Observed behavior:
    - Graph control is drawn abnormally large (larger than panel size; abnormally large fonts).
    - This is only seen with graphs with top X axes. 

    Hello -
    I'm not able to reproduce what you're seeing.  Could you please post a small example project that reproduces what you're describing?
    Thanks -
    NickB
    National Instruments

  • TDMS functions much slower in CVI 2010

    Hello everyone.
    Today I noticed that at least some TDMS functions are much slower in CVI 2010 compared to CVI 2009 SP1 and prior. I have created and attached a simple sample project that creates a TDMS file with about 3000 file level properties and tries to read it back in afterwards. On all releases prior to 2010, this needs less than 10 seconds. On 2010 it's around an hour, if not more! Unfortunateky this is pretty much a show-stopper for me. Any comments?
    Thanks, Marcel 
    Attachments:
    tdmsTimingTest.zip ‏3 KB

    Hello Marcel -
    What you've reported is actually a known issue, and is unfortunately considered to be expected behavior.  Let me try to explain:
    There was a relatively large refactoring of the underlying TDMS code in LabWindows/CVI 2010.  This refactoring was intended to more closely align our internal implementation to that of LabVIEW.  As a result of this refactoring, we were able to address some internal issues we had previously been unable to address, as well as more correctly handle the data stored in the TDMS file.  Unfortunately, this refactoring unmasked a performance issue that had always been present when reading a large number of properties one at a time.
    This performance issue was not uncovered for LabWindows/CVI 2010 because we had previously focused our performance testing on reading and writing data to a file, not metadata.  We considered it unlikely that a customer would have more than dozens of properties for any one channel or group or file, and as a result, the performance issues you've reported were overlooked.
    However, we did recently find the performance issues you've reported.  As a result, there will be a handful of undocumented functions for returning all (or a subset of) properties on a channel, group, or file in LabWindows/CVI 2010 SP1.  This will allow for performance in line with what you'd seen in LabWindows/CVI 2009 SP1 and earlier, as long as you are OK with grabbing all the properties at once.  These functions are undocumented because, in general, we don't release new features with service packs.  Also, the functions are a little more difficult to use than normal CVI APIs, so we have not yet determined how or when they will be publicly documented.  When LabWindows/CVI 2010 SP1 releases (later this summer), feel free to reply back to this post or send me a private message, and I'll work with you on the details of calling these undocumented functions.
    Out of curiosity, we'd like to know your use case for creating that many properties.  You're the first customer we've encountered using such a large number of properties, and we'd like to ensure that we are able to satisfy your use case in future versions of the API.
    Thanks for the report, and I'm sorry for any inconvenience this has caused,
    NickB
    National Instruments

  • Dynamic memory is corrupt (Labwindows/cvi 2010)

    I have a multi threaded application....where I have a buffers allocated ineternally in the threads,,...A user interface is present to abort the therad execution.
    Here is the code in one of the threads (NOTE: status is set by a user button to EXIT the program):
    int EthernetDataStructureThread (void *functionData)
        CmtSetCurrentThreadPriority (2);
        EthernetData GetData={0}, *data=NULL;
        data = &GetData;
        /* Use a buffer to read the data from the queue which is coming from TCP read with fresh data */
        const void *BufferEth;
        int BytesRead=0;
        int BytesWritten=0;
        char ReadErrorMessage[256];
        BOOL bitset = FALSE;
        if ( (BufferEth = (EthernetData*)malloc(EthernetDataSize)) != NULL)
            while ( !status )
                BytesRead = CmtReadTSQData (Queue_TCPRead_EthernetData, BufferEth, EthernetDataSize, TSQ_INFINITE_TIMEOUT, 0);
                memcpy (data, BufferEth, EthernetDataSize);
                /* Empty the queue so that we don't have data in next time. */
                CmtFlushTSQ (Queue_TCPRead_EthernetData, TSQ_FLUSH_ALL, NULL);
                //Pass on the data to the Main thread
                BytesWritten = CmtWriteTSQData (Queue_EthernetData_Main, BufferEth , EthernetDataSize, 1, NULL);
                if ( BytesWritten != EthernetDataSize)
                     free(BufferEth);
                    BufferEth = NULL;
                    exit(0);
                Delay(0.02);
            if (status && !bitset)
                free(BufferEth);
                BufferEth = NULL;
                bitset = TRUE;
        return 0;
    My problem is: free(BuffEth) always says Dynamic Memory is corrupt......When I put a breakpoint and keep seeing the resource tracking window, I can see it getting executed fine as the resource tracking window greys out the memory block....but then suddenly free wants to exceute again...and causes the "dynamic memory is corrupt" error.
    I am using LABWINDOWS /CVI 2010 SP1 in WinXP.
    Please help me ASAP....very much appreciated.
    Regards
    NITIN
    -Nharish

    Thank you for your reply Jackie.
    I am calling Free only once...there is an If condition there.
    See the attched video for my problem...Free frees the memory block (see the greyed out portion in resource tracking window but still the statement controls remains there and free executes again, throwing error).
    Do you  think it is some sort of bug in LABWINDOWS.
    See the attached video.
    -Nharish
    Attachments:
    FreeproblemLabwindows.avi ‏4781 KB

  • Error when trying to migrate project from labwindows 2010 SP1 over to VS2008

    I'm sure I've been successful back with this when running CVI 8.5 and VS2003 / 2005, but I keep gettin the following error when trying to do this with my current configuration. What am I missing?
    See attached image
    Regards
    Gavin
    Attachments:
    CVI-VS error.JPG ‏29 KB

    Not recently, but what I would say is that CVI 2010 SP1 was installed after my VS2008 installation, so it ought to be in the right order.... When I get a moment I'll reinstall the CVI runtime and see what happens. Its not critical that I get this fixed, as the project in question is so small, and as the important parts are almost competely ANSI C, it should be really easy to reconstruct in C# anyway. I'll let you know what happens anyway

  • Application crashes in Windows 7 64bit made in Labview 2010 sp1 f2 with Fault module name%3A lvrt.dll%2C version 10.0.0.4033 and exception code c0000005

    I build an application exe and then its installer along with run time environment.
    The installers instals the application correctly but when I try to execute the application, I get an error that application has crashed and Windows must close it down or search for solutions online with this additional information for the crash. 
    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: AGMS.exe
    Application Version: 1.3.0.0
    Application Timestamp: 4c24e8f5
    Fault Module Name: lvrt.dll
    Fault Module Version: 10.0.0.4033
    Fault Module Timestamp: 4c9273f4
    Exception Code: c0000005
    Exception Offset: 00005310
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 1033
    Additional Information 1: 0a9e
    Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
    Additional Information 3: 0a9e
    Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt
    I am using labview 2010 sp1 32 bit on a 64-bit machine, with the following specs
    Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
    Language: English (Regional Setting: English)
    System Manufacturer: Dell Inc.
    System Model: Dell System XPS L502X
    BIOS: Default System BIOS
    Processor: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (8 CPUs), ~2.0GHz
    Memory: 8192MB RAM
    Available OS Memory: 8106MB RAM
    Page File: 3457MB used, 12753MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7601.17514 32bit Unicode
    The exe /application runs fine on my PC but when I try to run it on another PC it crashes. The other PC has similar specs as given below
    Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
    Language: English (Regional Setting: English)
    System Manufacturer: LENOVO
    System Model: HuronRiver Platform
    BIOS: Default System BIOS
    Processor: Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz (4 CPUs), ~2.2GHz
    Memory: 4096MB RAM
    Available OS Memory: 4010MB RAM
    Page File: 1359MB used, 6658MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7601.17514 32bit Unicode
    I tried another machine, 64 bit of course, as I want to deploy my application on a 64bit PC, but still got the same problem.
    This other machine was from HP, iCore 3 (4 CPUs) 2.2GHz, 4GB RAM and running Windows Professional 64 bit.
    Now as I see it, it could be a Run-time environment mis-match error.
    For this I tried installing a 64 bit LVRTE from NI, but still no sucess.
    I checked DEP, for all 3 PCs and it was set to the following
    Turn on DEP for essential Windows programs and services only (first option).
    I am confused. I can not find a solution for this and it is really frustrating.

    But I am assuming that when I make the installer, the 32-bit Run Time Engine is appened with the installer, as show below
    Since from the picture you can see its including the support installers from '\Program Files (x86)\'
    The application runs queries to fetch data from database in SQL server 2008, and for that I am using a Microsoft SQL Native Client 2008 R2 64 bit ( this is the only version that installs on either PC, even the one on which I developed my LV Application).
    I am not using any driver, only toolkits for reports - and for that I un-checked the "Remove unused polymorphic VI instances" when making the executable, otherwise LV throws up an exception that share variable are not being included.
    Yes I did reboot every time after I ran the installation.
    Still getting the same error.

  • Access 2010 SP1 - random crashes relating to vbe7.dll

    We are experencing the same problem as described here in a post on
    Microsoft Answers.  However was are also still occasionally seeing the problem after uninstalling SP1. 
    Has anyone come across any better workarounds? 
    Microsoft: can we please have some information on when this is likey to be fixed - this is a major problem!
    After installing Office 2010 SP1, you may receive random crashes when opening objects in certain databases and when trying to open the VBA window in those databases.  If you look in the event viewer the crash info may look similar to the following:
    Faulting application: msaccess.exe
    Version: 14.0.6024.1000
    Stamp: 4d83e4fc
    faulting module: vbe7.dll
    version: 7.0.16.19
    stamp: 4d430aec
    Workaround:
    Microsoft is aware of the issue and it is currently being investigated.  In order to work around the problem, you can try the following:
    1.      Make a copy / backup of your database.
    2.      On the problematic machine decompile the database by running the following from a Run command line: MSACCESS.EXE <path to database file> /decompile
    (example: C:\Program Files (x86)\Microsoft Office\Office14\MSAccess.exe "C:\folder\database.accdb"  /decompile)
    3.      Close the database.
    4.      Open the database again normally.
    In addition to this, if you experience the crash please send the error report when prompted to do so after the crash.

    Hello,
    Have you tried the workaround? It should work after you decompile your databases.
    And if there is better solution released by Microsoft, you will be able to find them in certain KB like:
    http://support.microsoft.com/kb/2533794
    Sincerely,
    Max Meng
    Forum Support
    Please remember to
    mark the replies as
    answers if they help and
    unmark them if they provide no help.
    If you have any feedback on our support, please contact
    [email protected]

  • Performanc​e issues - CVI 2010

    Hi all,
    I have code I've compiled on a development machine - XP Pro with SP3 - and I'm seeing some performance issues on a similarly configured test machine.  2GB Ram, Pentium 4 CPU 2.8GHz.  I had our IT person clean off another machine for me to use exclusively for testing (the other machine is our Tester's PC) and he gave me one with an Intel Core2 4300 @ 1.80 GHz.  My code on my test machine runs like a top with NO problems. 
    We have another PC running Win7 on an Intel Core i5-2400 @ 3.10 GHz, RAM = 4GB.  The code should be screaming on this machine but we're seeing performance problems here, too, that I believe may be due to the OS - Win7 may be a real hog.
    Can anyone make sense of this?  Is the dual core that much better even though that CPU is rated lower in PassMark Bench Ratings (http://www.cpubenchmark.net/cpu_list.php).  We're trying to work all this out so we can advise the customer on which machine he needs to run our software.
    Thanks,
    Judy

    Hi Judy,
    Looking at the spreadsheet it seems unlikely that memory or cpu requirements are the root cause of the issue because the second machine in the spreadsheet with poor "performance" has almost twice the CPU clock speed and twice the physical memory of the fourth machine that runs well.
    It sounds like your application is a fairly complex application that involves both GUI components and instrument I/O so what needs to be done is determine what part of the application is causing the bottleneck. There are many different factors which if not considered properly when developing applications that can cause performance problems such as thread deadlocks, device driver problems with the instruments or other hardware, needing to adjust the sleep policy for GUI events, writing to TDMS files in CVI versions before 2010 SP1, having memory leaks in the application code, etc. There is also a KB called Improving Performance of LabWindows™/CVI Applications that describes some changes which may help improve performance.
    The overall message is that it is not only CPU speed and quantity of RAM available that can cause performance problems. A way to check the amount of RAM used by an application and CPU Utilization is to use the Windows 7 Resource Monitor to watch the application. This can be done by running Task Manager (ctrl + shift + esc), selecting the Performance tab and pressing Resource Monitor. This will open the Resource Monitor window where you can check CPU usage, Memory, Disk and Network usage for the application while it is running.
    Milan

  • Labwindows CVI 2010 and GetProcessAddress()

    I am using Labwindows CVI 2010 v10.0.1 after upgrading from version CVI 2010 v10.0.0. After the upgrade, I have a compile error from a statement that compiles just fine in the previous version. The error is:
    "Operands of = have illegal types 'pointer to __stdcall int function(int,pointer to char,pointer to char,pointer to char,int,pointer to char,pointer to char)' and 'FARPROC'."
    What causes this error is the following statement in the code:
    my_FP = GetProcAddress(dll_handle, "DLL_FUNCT");
    and the definition of my_FP is:
    int __stdcall (*my_FP)(int x, char y[], char z[], char *m, int g, char A[], char B[]);
    (function names and parameters have been changed for simplicity)
    As I said, this line compiles just fine in 10.0.0, but not in 10.0.1. Is there a specific update to the compiler that will cause this error? What can be done to fix this?
    Thank you very much for your time and help.
    Solved!
    Go to Solution.

    You're correct. This was caused by a change in CVI Windows SDK headers that took place in version 2010 SP1. The change was associated with bug fix #275934. Unfortunately, this bug fix introduced this undesirable side effect of requiring a cast for any function that returns a FARPROC function poinrter (such as GetProcAddress). Upon further reflection, this side effect is unacceptable, and needs to be corrected in the next release. This is being tracked internally with bug ID #336341.
    I'm really sorry for this inconvenience. Until the problem is resolved, using the typedef & cast solution that you already implemented is a valid workaround.
    An alternative workaround, in case you're worried about other projects, or other functions, where this error might also pop up, is to edit CVI2010\sdk\include\windef.h and replace the following FARPROC definitions (in lines 226 and 230, respectively):
    typedef INT_PTR (FAR WINAPI *FARPROC)(void);
    typedef int (FAR WINAPI *FARPROC)(void);
    with:
    typedef INT_PTR (FAR WINAPI *FARPROC)();
    typedef int (FAR WINAPI *FARPROC)();
    Doing this will avoid the problem throughout a given installation of CVI.
    Luis
    NI

  • Can not Open exe file that is created by Labview 2010 SP1

    Hi Everyone,
    My Operating system is XP .. I installed .net latest version but I can not open exe file. I try to open  exe file, then  crashes , quits without seeing any interface.
    I tried with another computer whose o.s is xp too. I can open exe file. I saw it is created by Labview 2010 Sp1
    I dont know what the difference is. I attached config file. 
    Attachments:
    TPS65175 C (Vcom only).ini ‏1 KB

    burak35 wrote:
    [..]Do  I need any other components besides .Net? 
    That's a question only the provider of the application can answer.
    You could also take a look into the system event log if there is an indication for the reason of the application failing to start properly. It is possible that certain services are required for the application, but they do not run on the machine.
    Another point is possibly missing rights. So you might want to test the application once with the option "Run as Admin" (right click menu item on the application shortcut or the exe itself).
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Timer( ) resolution in CVI 2009 SP1

    In the CVI 2009 SP1 Contents Help for Timer() function I find
    The resolution is normally 1 microsecond. However, if you set the useDefaultTimer configuration option to True, the resolution is 55 milliseconds.
    But if you click on the useDefaultTimer hyperlink, a new page is opened, where you can read that the resolution is 1 millisecond if you set useDefaultTimer to False.
    Which is the right resolution?
    I wrote my application considering 1 microsecond, but I found strange problems, and I think it is 1 ms.
    Vix
    In claris non fit interpretatio
    Using LV 2013 SP1 on Win 7 64bit
    Using LV 8.2.1 on WinXP SP3
    Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
    Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

    Hi vix,
    Thanks for bringing those documentation problems to our attention.
    1. There does seem to be a problem with a lot of the function prototypes in the .chm help in the CVI 2009 SP1 and 2010 versions, where an extra asterisk seems to have been added to a number of output parameters. We'll fix this and post a corrected version of the affected .chm files as soon as possible. In all these cases, the parameter data type as it appears in the Parameters section of the help topic is correct, as is the prototype in the corresponding function panel.
    2. Concerning the timer resolution issues, the async timer resolution is in fact 1 millisecond, as confirmed by the GetAsyncTimerResolution function. But note that asynchronous timers are a library in and of themselves, and are not covered by what is discussed in the documentation of the Timer() function or the useDefaultTimer option.
    The resolution of the Timer() function should be 1 microsecond, as of CVI 9.0 and later. The function documentation is correct. When that change was made, however, the documentation of the useDefaultTimer option was incorrectly not updated. It should say that "the performance counter timer provides a resolution of 1 microsecond".
    You mentioned that you didn't think that the resolution of the Timer() function was 1 microsecond. If you run the following code, what do you see?
    int     i;
    double  time[10];
    for (i = 0; i < 10; i++)
        time[i] = Timer();
    for (i = 0; i < 10; i++)
        DebugPrintf ("timer = %f\n", time[i]);

Maybe you are looking for