Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Having problems making Call Library Function Work
BCLioness
Member
07-16-2004 01:12 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I have tried reading other threads related to my problems, but can't figure out what to do. I am simply trying to use the call library function for a C++ program that receives 2 numbers and returns the sum (once I have this down, I intend to work with more complicated C++ programs for the project I am needed to work on). I have a function called 'add' in the C++ program that I finally figured out how to export (using previous forum threads) and so LabVIEW does see the function now. But when I run the VI, it gives me this error:
"LabVIEW: An exception occured within the external code called by a call library node.
This might have corrupted LabVIEW's memory.
Save any work to a new location and restart LabVIEW."
Do I really have to keep saving to a new location every time I try to run this and get this error? And what should I be looking at to stop this error from occuring? I have 2 controls for the input numbers on the front panel, and one indicator for the output. I put a break point after one of the controls and before the Call Library Function, it gives me the error after I step over the breakpoint.
I am thinking that maybe I am doing something wrong in my C++ program, but it is such a simple program I don't see what it could be.
I am running Microsoft Visual C++ 5.0 to create the .dll and LabVIEW 7.1.
Thanks for any input.
Lori
"LabVIEW: An exception occured within the external code called by a call library node.
This might have corrupted LabVIEW's memory.
Save any work to a new location and restart LabVIEW."
Do I really have to keep saving to a new location every time I try to run this and get this error? And what should I be looking at to stop this error from occuring? I have 2 controls for the input numbers on the front panel, and one indicator for the output. I put a break point after one of the controls and before the Call Library Function, it gives me the error after I step over the breakpoint.
I am thinking that maybe I am doing something wrong in my C++ program, but it is such a simple program I don't see what it could be.
I am running Microsoft Visual C++ 5.0 to create the .dll and LabVIEW 7.1.
Thanks for any input.
Lori
LarsRoe
NI Employee (retired)
07-16-2004 01:39 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
It sounds like you are using different calling conventions. In LabVIEW's Call Library Function dialog, there is an option for Calling Convetions that can be set to either C (cdecl) or stdcall (WINAPI). This has to match the DLL you are calling, so try the other option of what it is set to now.
See the pdf document titled "Using External Code in LabVIEW" for more details.
See the pdf document titled "Using External Code in LabVIEW" for more details.
07-16-2004 01:44 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Well that was much easier than expected. I had thought I tried that, but you got me to 'try' it again, and it worked.
Thanks Muchly,
Lori.
Thanks Muchly,
Lori.
LarsRoe
NI Employee (retired)
07-16-2004 02:04 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
You're welcome. You can also set LabVIEW as the target application in VC. This way, you'll run LabVIEW, and it will hit the breakpoints in your C code.
