07-03-2006 11:15 AM
07-04-2006 03:52 AM
Hi,
you don't say whether you're actually using Visual Studio, or if it's .net or borland or something enirely different, but the principal holds for all that allow external debugging capability.
You need to set labview.exe as the external process to run for your dll project, and then load up the .vi in labview that calls it. You then have the debugging features of LabVIEW (since you're in that environment) and when LabVIEW calls the DLL (must be made debuggable), the c++ environment is effectively running LabVIEW in it's memory space, so it will honour all the breakpoints in the c++ project code as they get called.
For Visual Studio 6.0 c++, have a look here :
http://windowssdk.msdn.microsoft.com/en-us/library/ms164704.aspx
and here
http://windowssdk.msdn.microsoft.com/en-us/library/605a12zt.aspx
Hope that helps
Sacha Emery
National Instruments (UK)
05-26-2014 09:11 AM
Hi,
Thanks SachaE for the explanation. In addition to that it might be useful to show the calling VI during the LabVIEW call (in case a sub VI does the call) + set a breakpoint onto the DLL call.