Debugging - Matrox 4Sight User Manual

Remote debugging on Matrox 4Sight using Microsoft Visual C++ 6.0
The DLLs without debugging information are Msvcrt.dll,
Msvcirt.dll, and Mfc42.dll. They are already installed on the
Matrox 4Sight unit.
The DLLs with debugging information are Msvcrtd.dll,
Msvcirtd.dll, and Mfc42d.dll. It might be necessary to copy
these files to your target computer for remote debugging if
the application is using them. These files can be found in the
C:\WINNT\SYSTEM32 directory on your development
computer.

Debugging

After having copied all relevant files, you can begin debugging
remotely from your development computer. The Matrox 4Sight
unit will use its local DLL's during the remote debugging
procedure. Note that for a MIL application, a MIL run-time
license will not let you debug your application, even if you are
debugging it remotely. The hardware key included with the
MIL development package must be connected to
Matrox 4Sight's parallel port. To begin debugging:
1. We suggest sharing one directory (either on the
development, the target, or another network machine)
common to both the development and target computers.
Edit and compile your application in this directory, move
any required third-party DLLs into this directory, and then
access these files in place. It is easier to share a directory;
otherwise, you will have to copy these files manually from
the development computer to the target computer.
2. On the development computer, load your project into
Microsoft Visual C++.
3. Select Settings from the Project menu. The Project
Settings dialog box is presented.
4. Choose the Debug property sheet.
5. Select General from the Category list box, and set the
following items:
Executable for Debug Session: Specify the name and
path of the executable file so that the development
computer can locate it.
59