dll crashes LabView 2013 Pro, but ok from EXE

[Blokk]

Hello,

I have started to have an older problem "escalated". I had a previous post about a dll which is playing an interface role between a program running under Windows, and LabView. The details are here:

http://forums.ni.com/t5/LabVIEW/installed-program-no-comm-with-driver/m-p/2659765/highlight/true#M79...

Note that, this is not a duplicate post, I just mentioned my recent problem there, when it was not that frequent.

(http://forums.ni.com/t5/LabVIEW/installed-program-no-comm-with-driver/m-p/2662503/highlight/true#M79...

Today -reason unknown- after a win system restart I cannot run my LabView code from the development environment. When I run the main VI, it crashes the whole LabView environment at the first dll call. This problem we had before too, but at the 2nd of 3rd try it ran OK. Today I tried like 30 times, also did many system restart. The native spectroscope software runs fine also.

Strange enough, if I run the build exe, everything works fine. The problem appears only when I run from LabView. There is no error code, only a window appeared at the first time, like I can send the error report to NI. I can dig into some log files tomorrow at the lab, I just need to know where I can look for it.

It looks like someone else also experienced similar behavior with external dll calling:

http://forums.ni.com/t5/LabVIEW/Problem-Dll-crashes-LabVIEW/m-p/2562667/highlight/true#M773565

"In the resulting application (Exe) it seems to work fine."

What is the difference between when the dll is built into the exe, and when it is run from LabView dev environment?

Thanks for any idea, and help!

(if nothing helps, I will just re-build the exe after program changes, but it slows down coding a bit 🙂

Last time we did not get feedback from the company who created this dll, I will try to contact again...)

[AnMu · Accepted solution]

Hi ,

you said you have read the discussion in the following link:

http://forums.ni.com/t5/LabVIEW/Problem-Dll-crashes-LabVIEW/m-p/2562667/highlight/true#M773565

Are you facing the exact same problem?

If yes, then there is not much we can do. LV is having a access contradication with your included DLL unless you have access to its source. You are not having these issues with the exe since this solely runs on the run time engine wheras the LV environment runs the code in a different way( For which LV reserves that particular memory on which your DLL is also trying to access.

[Blokk]

Hello,

Thanks for the info!

Actually I can live with this problem, since the project is almost 100% finished, and the little minor changes do not require test runs from the LabView editor.

I think I will just forward these discussions to the company, they should fix the dll on their side...

best regards,

ps.: i just mark your reply as a "solution", since it means that we cannot do too much on the LabView side

(but maybe a more informative error handling of the LV editor would be nice...but i do not know if it is possible with dlls...)