LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

DLL Call result: The Instruction at "0x02623811" referenced Memory at "0x02623811". The memory could not be "Read"

Dear Wireworkers

 

I have written a snal DLL call that fetches Data from a framegrabber to copy it into the right format for LabVIEW.

The DLL work perfectly but I always get the Error Msg:

      The Instruction at "0x02623811" referenced Memory at "0x02623811".
      The memory could not be "Read"
This sounds to me like a pointer problem.

The Msg apears only on the target system. Not in the runtime system.

The DLL must not be executed to produce this error. It always comes after the end of the application.

Please find attached the DLL call...

 

Any Ideas

With kind regards

Martin Kunze

KDI Digital Instrumentation.com
e-mail: martin.kunze@digital-instrumentation.com
Tel: +49 (0)441 9490852
0 Kudos
Message 1 of 2
(2,451 Views)

Dear Mr. Kunze, 

 

this error is being catched by the OS. It points to a read-access to an illegal address, mostly caused by a pointer-problem. 

 

Attached are some information how to troubleshoot such a problem.  

 

LabVIEW Application Error: The instruction at address x referenced memory at address y. The memory could not be read.
http://digital.ni.com/public.nsf/allkb/E8C5C452F04EF7BE86256EF50068CAAF?OpenDocument

Why Does LabVIEW Crash When I Call My DLL?
http://digital.ni.com/public.nsf/allkb/7253D2F0D91F68058625752F005AB672?OpenDocument

 

Debugging:  

 

Writing Win32 Dynamic Link Libraries (DLLs) and Calling Them from LabVIEW
(Troubleshooting the Call Library Function and Your DLL, )
http://zone.ni.com/devzone/cda/tut/p/id/4877

 

How Can I Debug My LabVIEW Executable?

http://digital.ni.com/public.nsf/allkb/3087D91EEADBAF3D862571D1004AF192?OpenDocument 

 

 

I hope this will help you out - esp. the debugging-section. 

 

 

With best regards

 

Ralf N. 

Application Engineering

Germany 

0 Kudos
Message 2 of 2
(2,422 Views)