ID | Known Issue |
---|
.NET and ActiveX |
44669
Return | The WordRpt_SetHeader function might not always work as expected.
Embedding pictures in a header does not work.
Workaround: N/A
Reported Version: 8.5 | | Resolved Version: N/A | | Added: 11/22/2010 |
|
284293
Return | Using a WebBrowser ActiveX control from a thread created in a LabWindows/CVI thread pool leaks memory.
Threads from a LabWindows/CVI thread pool, run using CmtScheduleThreadPoolFunction, will leak memory if they host a panel that displays a WebBrowser ActiveX control.
Workaround: N/A
Reported Version: 2009 | | Resolved Version: N/A | | Added: 03/08/2011 |
|
348295
Return | A panel containing an ActiveX control disappears when the mouse hovers over the control if the titlebar is not visible.
Workaround: If the control has a windowless mode, use the windowless mode.
Reported Version: 2009 | | Resolved Version: N/A | | Added: 07/22/2012 |
|
148778
Return | The ActiveX Controller Wizard does not support LONGLONG and ULONGLONG data types.
Workaround: Add the methods containing int64 parameters manually to the generated files.
Reported Version: 9.0 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
363992
Return | The first letter of exported functions in type libraries has inconsistent case behavior.
Workaround: N/A
Reported Version: 7.1 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
426545
Return | Creating an ActiveX Controller for a large type library, such as the Microsoft HTML Object Library, results in the message Maximum number of function tree nodes exceeded.
LabWindows/CVI is unresponsive while the ActiveX Controller Wizard generates the code, and the message appears after some time.
Workaround: Two ways to reduce the number of function panels:
-
- In the ActiveX Controller Advanced Options dialog box you can deselect objects that you will not use.
-
- On the Configure panel you can select Compatibility Options and change the Property Access Functions option to either Per Object or Per Server to significantly reduce the number of function panels used. Selecting either of these options might make it more difficult to access properties but all objects are still available.
-
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
Analysis |
306163
Return | The PeakDetector function does not recognize peaks of a sine wave when the sampling rate is very high.
If the peak is relatively flat because of the high number of points acquired at the high sampling rate, the PeakDetector function may not find the peaks.
Workaround: N/A
Reported Version: 2010 | | Resolved Version: N/A | | Added: 07/27/2011 |
|
Compiler |
237998
Return | Cannot link some uuid.lib symbols in a 32-bit program.
Workaround: N/A
Reported Version: 9.0 | | Resolved Version: N/A | | Added: 11/22/2010 |
|
291945
Return | Compiling a very large array in debug mode can be very slow.
For instance, compilation of the following code in debug mode would be very slow:
char *bigarray[30][25][1000][100];
int main (int argc, char *argv[]) { return 0; }
Workaround: Change the Debugging level option (Options»Build Options) to No run-time checking.
Reported Version: 2010 | | Resolved Version: N/A | | Added: 08/02/2011 |
|
335405
Return | Cannot link some odbccp32.lib symbols in a 32-bit program.
The issue exists with the odbccp32.lib that is included in the Windows 7 SDK.
Workaround: Use odbccp32.lib from the Windows Vista SDK instead.
Reported Version: 2010 | | Resolved Version: N/A | | Added: 07/17/2012 |
|
457821
Return | Including datasize.h and windows.h causes a typedef redefinition with different types error for the INT8 type definition.
Workaround: Modify datasize.h by commenting out the following line:
typedef char INT8;, which is line 104 by default.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 03/28/2014 |
|
412591
Return | Building a project that has a long file path causes LabWindows/CVI to crash.
Previous versions of LabWindows/CVI display a Filename is too long message instead of crashing.
Workaround: N/A
Reported Version: 2010 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
422103
Return | Some large source files take much longer to compile in LabWindows/CVI 2013.
The following is true of the new LabWindows/CVI 2013 compiler:
-
- Single-file compilation is slower in 2013, regardless of what comprises the code.
-
- Multi-file compilation is faster in 2013 because of concurrent compiles. Whether this completely makes up for the slower single-file compilation time or not depends on the number of files, size of the files, and so on.
-
- The 2013 linker is faster. This, together with the second bullet, will generally make builds faster in 2013.
-
- The build time of an Edit-Build-Debug cycle is also faster in 2013, but only marginally so, because the first and third bullets are applicable and mutually cancelling. The second bullet is not applicable in most cases.
-
- Compiling a PCH file is much faster in 2013. This only impacts the very first build of a project, the first build following a clean, or a rebuild.
-
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
424254
Return | Calling the assert macro generates a warning that code will never be executed when the LabWindows/CVI compiler can determine the outcome of the expression.
If the compiler can determine a condition will always have the same outcome, it will return this warning.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
430785
Return | Compiling causes an error: definition of the macro '_TARGET_FILE_VERSION_' conflicts with the definition used to build the precompiled header message.
This error can occur when using the auto-increment version feature in projects that include precompiled headers. A similar error occurs for _TARGET_PRODUCT_VERSION_.
Workaround: Do a rebuild instead of a build, after modifying a file that does not trigger the compilation of the precompiled header.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
471567
Return | Generating HTML help from source with array pointer type parameters results in an 'unknown' type generated in the help.
The following function declaration causes this type of error:
static int func(double (*dataArray)[4]);
Workaround:-
- Define your parameter using exclusively a pointer.
-
- Use a type definition to separate the type declaration of the array from the pointer as follows:
typedef double tArray[4];
static int func(tArray* dataArray); -
Reported Version: 2013 SP2 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
505265
Return | The FileExists function may fail in projects that use the Vision Builder AI engine.
A File Not Found error may occur when the FindFile function is used in a project that uses functions from the Vision Builder AI engine.
Workaround: Avoid using the FindFile function in a project which uses the Vision Builder AI engine. If it is necessary to use the FindFile function, it will be necessary to separate these two functions into separate projects. For example, the application could be implemented as two separate executables which communicate using shared variables.
Reported Version: 2012 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
516928
Return | Including a library (.lib), possibly of an old format, in both the project tree and the LoadExternalModule (LEM) Options dialog causes the following error: error: Input file is not a valid archive.
Workaround: Check a library in the LEM Add Files to Executable dialog only if you intend to use it later with LEM functionality (e.g., using GetExternalModuleAddr).
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
522704
Return | The build system incorrectly skips the compilation of a C file, if both the C file and an included H file have unsaved changes.
The problem can be described with the following steps:
-
- #include is added to foo.c.
-
- The project is built without saving foo.c
-
- foo.h is modified.
-
- The project is built. The build system incorrectly detects no reason to recompile foo.obj.
-
Workaround: Use the rebuild feature to rebuild the project.
Reported Version: 2013 SP2 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
357424
Return | Casting an int to a union does not cause a compile error.
Beginning with LabWindows/CVI 2013, GNU Extensions are enabled by default. Casting to union is a GNU Extension, and a warning is produced instead of an error.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
412828
Return | Building a distribution kit with a long file name can cause LabWindows/CVI to crash on Windows XP.
N/A
Workaround: N/A
Reported Version: 2012 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
430409
Return | The compiler may report the build error The compiler has run out of memory if <filename>.obj.cvidefprots exceeds 260 characters.
The compiler cannot create the <filename>.obj.cvidefprots in the config directory if the path exceeds 260 characters.
Workaround: Reduce the total path length of the project file. Reduce or increase the length of the source file name by twelve characters.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
434676
Return | Compiling large source files or functions may cause the compiler to display the following build error: The compiler has run out of memory.
N/A
Workaround: Split up the code from one large function into multiple smaller functions. Split up the source file into multiple smaller files to improve compilation performance.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
438833
Return | Incorrectly configured compiler define causes build error: <command line>:28:9: error: macro names must be identifiers.
N/A
Workaround: In Options»Build Options»Compiler Defines, refer to the Compiler Defines topic in the LabWindows/CVI Help to resolve the incorrect compiler define.
Reported Version: 2012 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
447401
Return | Compiler Defines return compile errors when porting code from LabWindows/CVI 2009 to LabWindows/CVI 2010.
In LabWindows/CVI 2009, multiple Compiler Defines are separated by a comma then a space. However, in LabWindows/CVI 2010, multiple Compiler Defines are expected to be separated by only a space. When compiling code in LabWindows/CVI 2010 that complies with the LabWindows/CVI 2009 Compiler Defines format, illegal character build errors are returned.
Workaround: Remove the commas separating the Compiler Defines.
Reported Version: 2010 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
475889
Return | GetExternalModuleAddr does not work for stdcall functions in import libraries created with Microsoft Visual Studio.
N/A
Workaround: Rebuild the VC import library with cdecl exports.
Note: This class of functions is obsolete. National Instruments recommends that you instead use the Interface to Win32 API functions LoadLibrary and GetProcAddress to load external modules.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
511542
Return | No access violation is thrown when trying to modify constant strings which are assigned to variables.
For example, the following code executes without an access violation:
<pre>char* text = "__text";
// Here, text will have the value "0_text". The constant string is modified here. An access violation should be thrown.
text[ 0 ] = '0';
// Here, text will still have the value "0_text" since the constant string was modified.
text = "__text";;</pre>
Workaround: Use strcpy.
<pre>char text[ 7 ];
strcpy( text, "__text" );
text[ 0 ] = '0';
strcpy( text, "__text" );</pre>
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
515817
Return | Generating help from source is incorrect on a multibyte OS if the source code tags or file name contains multibyte characters.
N/A
Workaround: N/A
Reported Version: 2012 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
543008
Return | The compiler incorrectly issues an uninitialized warning when a locally defined pointer to a structure is followed by a structure definition.
N/A
Workaround: Make sure the pointer to the structure is not followed by a variable definition to the same structure. You can also place the structure definition before the pointer definition, or place a definition of a variable of a different type in between.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
557448
Return | An incorrect build diagnostic 1, 1 ', but encoding is not supported is reported when a source file has UTF-16 BOM.
The corresponding build output message from the clang compiler is fatal error: UTF-16 (LE) byte order mark detected in 'Command-line Application.c', but encoding is not supported.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
564085
Return | The build for a DLL target does not detect mismatches between header declaration and function definition when exporting symbols from an include file.
This includes mismatches of calling convention and function prototype.
Workaround: If the header used to export symbols is included in the project, the compiler will detect mismatches.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
566083
Return | Old-style function definitions preceded by a prototype are diagnosed with the strict prototypes warning.
Warn if a function is declared or defined without specifying the argument types. An old-style function definition is permitted without a warning if preceded by a declaration that specifies the argument types.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
583937
Return | There are compile errors in the Interactive Window when including windows.h and winnt.h after compiling with only winnt.h included.
N/A
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
586821
Return | Selecting Compile with precompiled include file in Build Options causes Assertion Error in Windows Event Viewer.
N/A
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
588349
Return | A Compile error is thrown in the interactive window when calling the alloca() function.
When making a call to alloca() in Interactive Execution, it fails to build with the message, "error: use of unknown builtin '__builtin_alloca"".
Workaround: Instead of allocation memory on stack using alloca, use malloc to allocate memory on heap.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
591193
Return | When run-time checking is enabled, the first element of a multidimensional array of structures is initialized to NULL.
N/A
Workaround: Initialize array elements using asignment rather than inline initialization.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
555561
Return | The Options»Build Options»Require function prototypes option does not issue compile errors when function declarations are not declared using a full prototype.
N/A
Workaround: Enable -Wstrict-prototypes to benefit from a warning diagnostic when old-style function declarations are used.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 02/22/2017 |
|
706577
Return | Casting a double variable to a float produces unexpected results if compiled in 64-bit release mode with no optimizations.
Casting a double to a float in an application compiled in 64-bit release mode with no optimizations can result in unexpected behavior. The value assigned to the float may be completely different from the original double value. It may also result in a stack overflow.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: 2015 SP1 f2 and 2017 f1 patches | | Added: 8/16/2018 |
|
Debugging |
210086
Return | The LabWindows/CVI environment may hang while debugging with the Variables or Watch windows open.
Workaround: N/A
Reported Version: 2009 | | Resolved Version: N/A | | Added: 05/05/2010 |
|
335983
Return | Tooltip for symbol values during debugging may appear on top of the editor's scrollbar.
Workaround: N/A
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 07/24/2012 |
|
346034
Return | #define macros cannot be monitored in the Watch window.
If you define a watch expression for a macro, the Watch window will show ERROR: Unknown identifier and type at run time.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
370682
Return | When the cvidebug.exe process dies or is intentionally stopped, LabWindows/CVI cannot debug again until it has been restarted.
Each time you debug you receive a dialog box stating An unspecified error has occurred, probably due to corrupted data.
Workaround: Restart LabWindows/CVI.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
423739
Return | The DefineThreadSafeVar macro produces a warning indicating it will never be executed.
Workaround: This is an incorrect warning that can be ignored.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
438870
Return | Using the debugger to change the value of one variable in an anonymous nested structure changes it for all the variables in the structure with that name.
Workaround: Name the nested structures.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
438896
Return | LabWindows/CVI does not display a warning message when both a main and a WinMain entry point are defined in a source file.
When main and WinMain are both defined in a source file, only the WinMain entry point will execute at run time. LabWindows/CVI does not warn that main may not execute.
Workaround: N/A
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
442184
Return | Interface to Win32 API functions cannot be run in the Interactive Execution window.
Linker errors occur when Interface to Win32 API functions are used.
Workaround: Complete the following steps to work around this issue:
-
- Create an empty function panel with the same name as the Windows SDK library that you want to use.
-
- Save the function panel next to the Windows SDK .lib or copy the Windows SDK .lib next to the function panel.
-
- Load the function panel or reattach the program file (Instrument»Edit»Reattach Program).
-
- Verify that step 4 succeeded: Instrument»Edit»Show Info.
-
- Enable Options»Environment»Include loaded instrument drivers in Interactive window.
-
- Run your code snippet.
-
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
456208
Return | The Source Code Browser window displays the same reference to a macro multiple times.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
460794
Return | The Available Types dialog box in the Watch and Variables and Call Stack windows do not display the full list of types.
The list contains only types that are referenced in the application.
Workaround: If the type you want is not in the list, you can create a Watch Expression that casts the value to the type you want. For example, if you want to interpret variable foo as an unsigned char, and unsigned char is not in the list, you can create a Watch Expression for (unsigned char)foo.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
460799
Return | The Watch and Variables and Call Stack windows display the type incorrectly after using the Interpret As option multiple times.
If you interpret an int as a char and then interpret it as an unsigned int, the window will show the type as unsigned int (char (int)). The window should show the type as unsigned int (int).
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
461757
Return | The Break On Change state of a watch expression is lost when stopping and restarting execution or unloading and reloading a workspace.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
464146
Return | Setting a breakpoint from Breakpoints dialog box on an invalid line while debugging an application causes uncommitted changes in the dialog box to irreversibly take effect.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
464507
Return | Running the Interactive Execution window a second time after finishing a run of the interactive statements with the Finish Function option causes the Interactive Execution window to crash.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
464904
Return | The Watch and Variables and Call Stack windows do not mark the item for a pointer to a variable as red if the variable value changes.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
430376
Return | The Variables and Call Stack, Watch, and Array Display windows do not show the contents of char arrays with more than 252 unprintable characters.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
434406
Return | LabWindows/CVI no longer displays a warning while debugging a real-time application if threads are still running on the target when RTmain exits.
Workaround: N/A
Reported Version: 2012 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
437356
Return | Stepping over a function call located at the last line in the enclosing lexical scope causes a Step Into instead of a Step Over.
Workaround: Make sure the last statement is not on the same line as the closing curly brace.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
438839
Return | LabWindows/CVI displays incorrect or no values for CmtThreadLockHandle and CmtTSQHandle variables when the variables are declared as int.
Workaround: Declare the variables as either CmtThreadLockHandle or CmtTSQHandle instead of int.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
443138
Return | The Interactive Execution window does not allow immediate termination when execution is suspended due to a break on change on variable value.
Workaround: Step Over to the next step point or Continue to the next breakpoint.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
447051
Return | If the LabWindows/CVI debugger crashes (cvidebug.exe), all of the entries from the Watch window are cleared. Once you begin a new debugging session, the entries are restored to the Watch window.
This scenario may cause LabWindows/CVI to become unstable.
Workaround: Restart LabWindows/CVI.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
460394
Return | The Resource Tracking window shows freed resources as allocated if resource tracking is disabled after allocation.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
463635
Return | Opening the Graphical Array View for large, dynamically allocated arrays from the Array Display window causes an Index passed is out of range error.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
464563
Return | LabWindows/CVI does not allow you to attach to a 64-bit process running on a remote system.
When you attempt to attach to a 64-bit process running remotely, you receive an error stating The current project configuration is not compatible with the debugger.... The Build»Configuration menu selection also becomes out of sync with the configuration displayed in the status bar at the bottom of the editor.
Workaround: You can set the executable and command line correctly for the remote target system using Run»Specify Executable and Command Line and then you can select Run»Debug MyApplication.exe to launch the 64-bit process on the remote machine and debug it.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
466209
Return | The DebugPrintf function truncates large strings when printing to the Debug Output window.
Workaround: Split long strings into multiple print statements.
Reported Version: 9.0 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
466763
Return | LabWindows/CVI does not show enough digits of precision in tooltips or the Variables and Call Stack window.
The display has a 15-digit limit.
Workaround: N/A
Reported Version: 6.0 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
466921
Return | Running a function using its function panel results in an Interactive Execution Unresolved symbol error even if the Include loaded instrument drivers in Interactive window Environment dialog box option is enabled.
Workaround: Save your project after loading the instrument driver.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
469910
Return | LabWindows/CVI hangs when stepping through code for a console application and choosing Set Next Statement on the previous line after closing the console window while suspended.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
470486
Return | The Interactive Execution window incorrectly excludes the line and offsets the execution highlighting when adding a variable declaration on an instruction line.
Workaround: Do not declare variables on instruction lines in the Interactive Execution window.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
470948
Return | The Interactive Execution window does not allow stepping into the main function of a project.
Workaround: The Interactive Execution window allows stepping into the main function when execution is suspended in the project during a debugging session.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
472987
Return | The Parameter type incompatible with format specifier non-fatal run-time error does not display source location when 64-bit variables are used in code that causes the run-time error in the Debug64 configuration.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2014 |
|
502946
Return | The LabWindows/CVI debugger does not recognize variables that include the $ symbol as part of the variable name.
If you view the value of a variable with a $ in its name in the Variables window while debugging, you will see an Error: Unrecognized Identifier error.
Workaround: The C language specification states that $ is not a valid character to include in a variable name, so it is best to avoid using this character in variable names. This will prevent the error from occurring in the Variables window.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 10/29/2014 |
|
465367
Return | If the data slice in an Array Display is changed, the numeric controls, Row and Column, in the Go to Cell dialog correctly change their ranges, but Go to Cell does not go to the correct cell.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
470673
Return | Changing the data slice and displaying the format of a 2D char array causes the Array View to become unusable, if the first dimension of the array is bigger than the second.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
472358
Return | Terminating execution while the Watch window is closed causes watch expressions to be duplicated.
This can lead to debugging performance decrease as the number of watch expressions increases each time an execution is terminated.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
473458
Return | The Variables and Call Stack window occasionally shows ERROR: Unexpected character. when changing the specific type for a variable.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
477649
Return | An incorrect uninitalized variable non-fatal run-time error is generated for partially initialized arrays inside of structs.
Workaround: Initialize the array completely or turn off run-time error checking.
Reported Version: 2013 SP1 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
478665
Return | A Graph doesn't have that many cursors error appears when debugging an application with multiple arrays shown in the Graphical Array View.
Workaround: Open only one Graphical Array View at a time.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
479326
Return | The tooltip for an empty field on a function panel displays an = ERROR: Unexpected end of input. error when execution is suspended during debug.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
487428
Return | You receive a non-fatal run-time error, Attempt to read beyond end of string, when specifying a string member of a struct returned by a function as the source input for sprintf.
Workaround:-
- In the struct declaration, specify the string as a char array such of finite size.
-
- Alternatively, you can also use the strcpy function instead of sprintf to perform this action.
-
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
503717
Return | Debugging a project while concurrently debugging statements in the Interactive Execution window causes LabWindows/CVI to stop responding to commands.
Workaround: Stop debugging in the Interactive Execution window before debugging a project.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
504099
Return | A linker error will occur if a global variable is referenced in the Interactive Execution window and if the project which defines the global variable is being debugged.
If a statement such as extern int x; is used in the Interactive Execution window while the project which defines the variable x is being debugged, attempting to run statements in the Interactive Execution window will result in a linking error.
Workaround: Declare the global variable in a second source file. Alternately, run the Interactive Execution window statements while not debugging the project which defines the global variable.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
515028
Return | When trying to browse for the members of a structure () inside the Watch window, no browse info is found.
Workaround: Call browse info from the source rather than from the Watch window.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
515433
Return | When a compilation error occurs while running a function panel interactively, information about which function panel field caused the compilation error is not shown.
Workaround: Double-click the error in the Build Output window to see where the failure occurs in the Interactive Execution window.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
515436
Return | When using a user-interactive function (e.g., printf) in the Interactive Execution window, the console is not closed when execution finishes.
Workaround: Select Build»Clear Interactive Declarations to close the console.
Reported Version: 2012 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
515499
Return | Active breakpoints in the Interactive Execution window are hit when running function panels interactively.
Workaround: Toggle breakpoints in the Interactive Execution window before running a function panel.
Reported Version: 2012 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
515639
Return | An uninitialized pointer in a structure cannot be modified in the Variables and Call Stack and Watch windows. In the Watch window the pointer has the value Uninitialized.
Workaround: N/A
Reported Version: 2015 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
519172
Return | If you try to stop a program running in the Interactive Execution window after the cvidebug.exe process has been terminated, the editor crashes.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
533817
Return | The editable data tooltip does not display characters after a newline character.
Workaround: Use the Watch window or the Variables and Call Stack window to correctly view the variable's value.
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 08/03/2015 |
|
438921
Return | The Variables, Call Stack, and Watch windows display incorrect indices for multidimensional arrays with one dimension of size one.
If a multi-dimensional array has one dimension of size one, expanding an element corresponding to this dimension is displayed with elements from indices zero to the end of the array in the Variables and Call Stack and Watch windows.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
439442
Return | Compilation errors in the Interactive Execution window do not correctly specify the error location.
N/A
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
439443
Return | The Interactive Execution window displays error dialogs when run with empty contents after pressing Edit»Clear Window.
The following error dialogs are displayed: The interactive window was terminated unexpectedly and You are not debugging a process.
Workaround: Manually delete the contents of the Interactive Execution window.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
439990
Return | The Interactive Execution window does not honor disabling Break on»First Chance Exceptions or executing SetBreakOnFirstChanceExceptions (0);.
N/A
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
442198
Return | 64-bit addresses are truncated in the GetExternalModuleAddrEx and GetExternalModuleAddr Function Panels.
N/A
Workaround: Open the Interactive window and hover over the result of GetExternalModuleAddrEx or GetExternalModuleAddr to see the full address.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
449641
Return | Details are not displayed when loading an invalid file in the Resource Tracking window.
When trying to load an invalid file in the Resource Tracking window, a dialog appears that states: "Error in file '' on line".
Workaround: N/A
Reported Version: 2009 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
449642
Return | Loading a corrupted file into the Resource Tracking window can crash LabWindows/CVI.
N/A
Workaround: N/A
Reported Version: 9.0 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
450318
Return | When an Interactive Execution contains an unclosed brace the code does not execute and an error is not generated.
N/A
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
453270
Return | Graphical Array View does not work for 2D arrays with a dimension of size one.
N/A
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
456818
Return | If a function contains a function declaration, the Source Code Browser incorrectly lists the declared function in the Called from view pane of a function called after the declaration.
For example, the following code calls foo2 from main, but the Source Code Browser incorrectly lists foo2 as being called from foo instead of main:
void foo2(void);
int main (int argc, char *argv[])
{
int foo(void);
foo2();
return 0;
}
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
460215
Return | When suspended at a breakpoint on a closing brace, values of variables within the lexical block are not shown in the Watch window or Variables and Call Stack window.
N/A
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
463300
Return | Interactive Executions only display errors from included header files the first time they are built.
N/A
Workaround: Select Build»Clear Interactive Declarations or resolve the build error before building a second time.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
463922
Return | If there are expanded items in a Watch window after running an Interactive Execution, opening a different project displays the dialog There are no items in the list control.
N/A
Workaround: Clear the interactive execution before opening a different project.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
464227
Return | Editing the value of a variable in a Watch window displays Value illegal or out of range after running an Interactive Execution.
N/A
Workaround: Edit the value in the Variables or Memory window.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
473970
Return | Object files that use CVI library functions do not produce user protection errors when called from LoadExternalModule.
N/A
Workaround: Produce a .lib file instead to call from LoadExternalModule. Alternatively, move the code from the object file into your main program.
Note: This class of functions is obsolete. National Instruments recommends that you instead use the Interface to Win32 API functions LoadLibrary and GetProcAddress to load external modules.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
478903
Return | In the Variables and Call Stack window, the "[Frames below may be incorrect or incomplete.] entry disrupts navigation with the Up Call Stack and Down Call Stack buttons on the toolbar.
N/A
Workaround: Double click an item on the stack to navigate to that item.
Reported Version: 2013 SP2 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
482391
Return | When running an Interactive Execution while not suspended on a valid steppoint, CVI incorrectly reports "LabWindows/CVI could not launch the interactive window. Please repair your installation of LabWindows/CVI".
The correct message is "The operation is available only when you are suspended on a valid steppoint. Step Over to the next steppoint or Continue to the next breakpoint".
Workaround: N/A
Reported Version: 2013 SP2 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
510665
Return | View Variable Value only shows the first element of char* variables in the Array Display when the char* variable value is set using CA_BSTRGetCString.
N/A
Workaround: Open the variable from the Variables and Call Stack window.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
515795
Return | Red highlighted text in the Memory window is not always reset after every execution.
N/A
Workaround: The Watch window correctly highlights a variable value in red if it has changed since the last time a program was suspended.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
515797
Return | Editing a value in the Memory window does not highlight that value in red when using the Memory window for the first time after opening a project.
N/A
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
541876
Return | Watch expressions that are offset from a declared symbol's address are not editable.
N/A
Workaround: N/A
Reported Version: 2012 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
553889
Return | The Watch window shows the global variable address rather than the thread-local address for variables that use the __thread storage class.
N/A
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
568788
Return | The Type of character arrays does not update in watch expressions when you perform pointer arithmetic on them.
N/A
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
570889
Return | Accessing an array element of a pointer to an incomplete structure that is dynamically allocated as an array of fixed structures causes a Dereference of out-of-bounds pointer user protection debugging error.
The following code can reproduce this error:
<pre>
#include <ansi_c.h>
typedef struct THING {
unsigned int t_id[ 1 ];
} Thing;
#define THING_COUNT 2
int main( void )
{
Thing* things;
things = ( Thing* )calloc( THING_COUNT, sizeof( Thing ));
( things + THING_COUNT -1 )->t_id[ 0 ];
}
</pre>
Workaround: Turn off run time checking or avoid using incomplete structures.
Reported Version: 2012 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
580336
Return | LabWindows/CVI displays an error that reads Another debugging process is already in progress when the Attach to Process dialog is opened after running statements in the Interactive Execution window.
N/A
Workaround: Clear the Interactive Execution window.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
591529
Return | After changing the type of a local variable using the Interpret As option from the Variables and Call Stack window, the displayed type is incorrect.
Use: <new type>(<declared type>), instead of: <new type>(<old type displayed>).
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
591577
Return | The debugger highlights all expressions in a multi-variable declaration block broken over multiple lines rather than highlighting individual declarations.
<pre>// Setting a breakpoint on the line with y = 2; causes the debugger to highlight starting at int x...
void example( void )
{
int x = 1,
y = 2;
}</pre>
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 08/22/2016 |
|
Development Environment |
189843
Return | The Perforce 2009.1 client may cause LabWindows/CVI 2009 to crash.
LabWindows/CVI may crash when the Perforce SCC DLL is unloaded.
Workaround: Upgrade to the Perforce 2009.2 client.
Reported Version: 8.1 | | Resolved Version: N/A | | Added: 05/05/2010 |
|
193733
Return | Launching the DataSocket Binding dialog box may cause LabWindows/CVI to hang on Windows 7.
Workaround: Switch away from LabWindows/CVI to another application, and then switch back to LabWindows/CVI.
Reported Version: 2009 | | Resolved Version: N/A | | Added: 05/05/2010 |
|
216549
Return | LabWindows/CVI installs KeyHelp.ocx, which contains a security vulnerability.
For more information, refer to this link.
Workaround: This component is used for help tooltips in the LabWindows/CVI User Interface Editor. It can be safely prevented from being used in IE by using the Microsoft kill bit mechanism. The CLSIDs for this control are: {16DDBCA2-9F0B-4927-9315-62D8893FC7E8}, {B7ECFD41-BE62-11D2-B9A8-00104B138C8C}, {2603E4AA-D6F2-447E-8B9B-BE8F4CFCD79B}, {D03D48E0-D399-11D2-B9A8-00104B138C8C}, {7773D66A-023C-4791-98BE-0AEBEFEF16B2}, {EAEED2BE-6AEB-4C48-B18C-F03EEDF9EED8}, {338E6F5B-0988-4EC5-9805-82224A9AC4FF}, {45E66957-2932-432A-A156-31503DF0A681}, {1E57C6C4-B069-11D3-8D43-00104B138C8C}, {85BD2BC1-D3CD-11D3-8BF4-00104B138C8C}.
Reported Version: 2009 SP1 | | Resolved Version: N/A | | Added: 09/17/2010 |
|
227324
Return | LabWindows/CVI cannot copy files to the VXIPnP directories on Windows Vista and later.
These directories are locked by default, which is not the correct behavior.
Workaround: Install VISA, which will unlock these directories.
Reported Version: 2009 | | Resolved Version: N/A | | Added: 03/10/2011 |
|
289314
Return | User-defined types always receive an asterisk when used as output types in function panels.
For instance, if you define a custom type as
typedef char[256] String255;
you would not want it to have an asterisk appended to it when used as an output type.
Workaround: N/A
Reported Version: 6.0 | | Resolved Version: N/A | | Added: 03/24/2011 |
|
308191
Return | A multi-project workspace with projects targeting both 32-bit and 64-bit can incorrectly display import libraries.
For example, consider the case where you have a workspace with two projects. If both projects have import libraries associated with them, and one project is 32-bit and one project is 64-bit, the bitness marking of the import libraries may be confusing. If the 64-bit project is the active project, the import libraries of the 32-bit project will show as dimmed and 64-bit. Then, if you make the 32-bit project the active project, the bitness of its import libraries will show correctly, but the import libraries of the 64-bit project will now display as 32-bit and dimmed.
Workaround: N/A
Reported Version: 2009 | | Resolved Version: N/A | | Added: 07/27/2011 |
|
329035
Return | LabWindows/CVI Conversion Wizard does not transfer 'Compile with precompiled include file' setting to 'Precompiled Headers' setting in Microsoft Visual Studio.
Workaround: N/A
Reported Version: 9.0 | | Resolved Version: N/A | | Added: 01/09/2012 |
|
332047
Return | LabWindows/CVI stops responding while searching for an inaccessible network location.
When LabWindows/CVI is searching for a file at a network location that is not available, the environment stops responding.
Workaround: The search times out after about 2 minutes and the environment will resume. Avoid attempts to access network locations that may not be available.
Reported Version: 8.5.1 | | Resolved Version: N/A | | Added: 01/10/2012 |
|
322905
Return | Files in a project may not display source control icons when a LabWindows/CVI project is associated with the Perforce client.
If the Perforce Workspace root path has different casing than the actual path, then the icons do not display.
Workaround: N/A
Reported Version: 2010 | | Resolved Version: N/A | | Added: 02/15/2012 |
|
333837
Return | LabWindows/CVI projects are not handled properly when adding them from new workspaces in instances of LabWindows/CVI created from just-in-time debugging.
Adding or removing a project from the Project Tree in an instance of LabWindows/CVI created by the just-in-time debugger can cause unexpected behavior.
Workaround: Do not add projects to the Project from instances of LabWindows/CVI created by the just-in-time debugger.
Reported Version: 2010 | | Resolved Version: N/A | | Added: 02/15/2012 |
|
334920
Return | Corners of Source Editor windows are painted black in non-tabbed Workspace when opened.
When opening a workspace that has the Show Tabbed Workspace option disabled and at least one source code window open, the top corners of the Source Editor windows are painted black.
Workaround: N/A
Reported Version: 9.0 | | Resolved Version: N/A | | Added: 02/15/2012 |
|
357212
Return | The save icon does not dim after saving a file.
After a file is saved, the save icon is not dimmed. Once you click anywhere in the LabWindows/CVI editor after saving, the icon will then dim.
Workaround: N/A
Reported Version: 2012 | | Resolved Version: N/A | | Added: 07/17/2012 |
|
361958
Return | The Project Tree does not auto-hide when a UIR file is opened.
Other file types do auto-hide the Project Tree. This behavior occurs only if you enable the Auto hide Project Tree and Library Tree option in the Environment dialog box.
Workaround: N/A
Reported Version: 9.0 | | Resolved Version: N/A | | Added: 07/18/2012 |
|
363196
Return | Attribute passed is not valid error when declaring a variable in a function panel.
The error is incorrectly displayed and can be ignored.
Workaround: N/A
Reported Version: 2012 | | Resolved Version: N/A | | Added: 07/18/2012 |
|
347511
Return | Microsoft Visual Studio does not rebuild a LabWindows/CVI project if a UIR file changes but its header file does not.
Workaround: N/A
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 07/22/2012 |
|
347986
Return | The Load UI resource file dialog box in the User Interface Localizer utility unloads the currently loaded localization.
If changes have been made in the loaded file, a dialog box prompts you to save.
Workaround: N/A
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 07/22/2012 |
|
356708
Return | The Source window cursor can persist after selecting text and editing a variable tooltip.
This behavior can cause two cursors to exist at the same time.
Workaround: Scroll the Source Editor window up/down to make the old cursor go away.N/A
Reported Version: 2009 | | Resolved Version: N/A | | Added: 07/22/2012 |
|
337770
Return | Setting LabWindows/CVI to "Run as administrator" will open a new instance of LabWindows/CVI each time you open a file associated with LabWindows/CVI.
Workaround: If you want to use LabWindows/CVI as administrator you can check the "Run as administrator" option from the Advanced button of the Shortcut tab instead of the Compatibility tab. You can access these options by right-clicking the LabWindows/CVI icon on your desktop and selecting Properties.
Reported Version: 8.5 | | Resolved Version: N/A | | Added: 07/24/2012 |
|
333302
Return | Auto Backup will provide an error if the file is marked as read-only.
This behavior is common if the file is stored in source control. Auto Backup may also take effect even if the file was not modified.
Workaround: Disable Auto Backup in Environment Options.
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 07/25/2012 |
|
335488
Return | Excluded import libraries that represent both 32-bit and 64-bit .lib files are no longer dimmed after switching configurations.
The .lib file is excluded but is not dimmed.
Workaround: N/A
Reported Version: 2009 | | Resolved Version: N/A | | Added: 07/25/2012 |
|
366229
Return | The CVIXMLGetNumChildElements function does not count child elements included in an XML entity.
Workaround: N/A
Reported Version: 7.0 | | Resolved Version: N/A | | Added: 08/13/2012 |
|
440070
Return | The Find Next feature of the Find dialog box does not move to new results on subsequent uses.
If you do not move the text caret from the first result you find and subsequently click Find Next from the Find dialog, you stay at the same result.
Workaround:-
- Navigate search results using the Find Results pane.
-
- Press <F3> to navigate the results.
-
Reported Version: 6.0 | | Resolved Version: N/A | | Added: 12/06/2013 |
|
390670
Return | When you add a line continuation character \ to the end of a comment line initiated by the \\ symbol, the syntax highlighting feature does not continue to the next line, indicating the next line continues the comment.
This behavior can be demonstrated with the following code snippet:
\\This is a comment. \
This is also a comment.
Workaround: Do not use a line continuation \ to break a comment between lines.
Reported Version: 6.0 | | Resolved Version: N/A | | Added: 03/28/2014 |
|
439323
Return | LabWindows/CVI ignores changes made in the Environment Color Preferences dialog box in one of three panels in the Variables and Call Stack window
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 03/28/2014 |
|
451665
Return | The UI to Code Converter generates code containing an undefined function, InsertCtrlInCtrlArray.
InsertCtrlInCtrlArray was renamed to InsertCtrlArrayItem in LabWindows/CVI 2010.
Workaround: Replace all occurrences of InsertCtrlInCtrlArray with InsertCtrlArrayItem.
Reported Version: 2010 | | Resolved Version: N/A | | Added: 03/28/2014 |
|
369029
Return | The compile process does not wait for user response about missing include statements for header files.
In versions of LabWindows/CVI previous to 2013, compiling a project with missing header files caused a dialog box to appear, prompting you to include the missing headers. The compile process did not continue until the dialog box was dismissed. Now, the compile continues despite the dialog box, and the project has to be rebuilt after adding the missing headers.
Workaround: N/A
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
375449
Return | Upgrading LabWindows/CVI breaks paths to Clang in .ecc configuration files.
Workaround: Edit the .ecc file to point to the version of LabWindows/CVI you are trying to use.
Reported Version: 2012 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
375463
Return | File icons may obscure full pathnames in the Project Tree.
Workaround: N/A
Reported Version: 8.5 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
383011
Return | Unable to close the Open GL plot Properties dialog box after right-clicking the Open GL plot twice while the dialog box is open.
Workaround: N/A
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
391648
Return | Show Completions (<Ctrl-Space>) does not list members in anonymous structures or unions.
Workaround: Do not use anonymous, nested structs. Declare nested components using named fields.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|
403299
Return | The Functions in File ring is not wide enough to display some function names.
Workaround: Open the drop-down view to see the function names in full length.
Reported Version: 2013 | | Resolved Version: N/A | | Added: 05/07/2014 |
|