LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

standard I/O error window popup

hello :
        I am facing with a desperate  trouble. I have completed the  program code and ".uir" design, and when I Compile and execute them, there is no error appear, however when bringing datas and processing them use it, it would popup a standard I/O error window . what's wrong with them?
    ioerror.jpg
        hopping for your answer.
0 Kudos
Message 1 of 6
(3,515 Views)

This is the Standard I/O windows where somebody writes "error" message: this may happen if you have left somewhere in your code a printf () statement; you could start searching for such a line. CVI offers DebugPrintf () function that is useful in that it writes to CVI debug window and does nothing in a compiled executable so if you want to have some log message while developing the program you could switch to DebugPrintf instead of prinf ().

Are you using some external module or library? In one case I had a problem similar to yours and didn't find a reason in my code so I supposed some message could be raised from a third-party library I was using in that program.



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 2 of 6
(3,492 Views)

I am sorry, I can't understand what you say. I am a new user. And I know little about computer operating principle.  Can you explain it in detail?

0 Kudos
Message 3 of 6
(3,471 Views)

CVI can use a console (sort of command prompt window) to output messages from specific functions. This console is called Standard I/O window and is exactly the one you are seeing running your app. Now, printf () is the most probable cause of this window to appear, but there are several other instructions that can cause this to happen: this old knowledgebase article lists some of them. You may check if your app is using any of them.

 

Standard I/O behaviour can be modified: see this document for reference; look also SetStdIOWindowOptions () command. Consider also this forum thread, which can be useful if calls to those functions is included in some external library you are using that you cannot modify.



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 4 of 6
(3,455 Views)

I know how to solve this problem. Just share with thoes who are confronted with this probelm. Thank you for your enthusiasm.

 

11.jpg
0 Kudos
Message 5 of 6
(3,403 Views)

by unticking mark in Use console window for strd I/O WHEN dbugging maybe causing problem

will solve my problem huh??

and Iam using sprintf this also causong problem huh?

0 Kudos
Message 6 of 6
(2,954 Views)