Determine What Calls Are Made by My DLL or Executable in LabWindows™/CVI™

Updated Oct 9, 2018

Reported In

Software

  • LabWindows/CVI

Issue Details

  1. I have an executable that makes function calls to one or more dynamic link libraries (DLLs). Is there a way to determine what calls are made by my executable?
  2. I have a primary DLL that makes calls to a secondary DLL. Is there a way to track the calls the primary DLL makes to the secondary DLL?

Solution

There is a utility called Dependency Walker that provides a solution to the above two cases. It scans any Windows module (.exe, .dll, .ocx, .sys, etc.) and builds a tree diagram of all dependent modules, along with a list of functions called in each module. It catches all dependency types, including dynamic ones, that are loaded at run-time. 

The latest version of Dependency Walker is version 2.2 and it can be downloaded from dependencywalker.com.

As of LabWindows/CVI 6.0, the Source Code Browser utility was added that enables you to cross reference each function and variable across your project. For more information view the LabWindows/CVI Help and the Related Links section.

WAS THIS ARTICLE HELPFUL?

Not Helpful