LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Unhandled exception 0xC0000005 in my exe

I have a Labview application that controls property nodes and methods of a Visual Basic ActiveX DLL. The methods and properties work fine, but when I exit my exe I get a Windows error which brings up the option to email data to Windows. If I press the Debug button, I see that the error is due to an unhandled exception at 0xC0000005: Access violation. This error does not ocurr when running the same code in the development environment, and also does not happen if I remove all code related to the Visual Basic ActiveX DLL. The programmer responsible for the AxtiveX code says there is no problem with this code, it has been used for years in his environment (visual basic only). I noticed also in the debug window a mention of the use of "COMSTAT" and that this is no longer supported by windows.
 
I am also seeing that my exe is not being removed from the processes tab of the Windows Task Manager when I close the app. (This can cause all sorts of trouble the next time you run, and when you try to re-build the app)
 
If anyone can help with this, it would be most appreciated.
 
Thanks,
 
Howard Spec
0 Kudos
Message 1 of 2
(4,470 Views)
Howard,
an access violation lets you know, that some memory area has been violated.
This happens, if e.g. the DLL writes to a memory location controlled by LabVIEW, but the memory area is not large enough to take the data. Check your LabVIEW code for the memory buffer sizes that you pass to the DLL.

If you have access to a debugger: Debug your application. Many debuggers report so-called "First chance exceptions" (if I remember correctly an access violation is one) and what your application was doing when violating.
 
If you feel sure that you are not responsible for the access violation it would be great if the programmer of the DLL (your colleague, I hope) would do a debug session with you.
Hope this helps, Guenter
0 Kudos
Message 2 of 2
(4,463 Views)