Table of Contents
Advertisement
60
Chapter 4: Developing an application for Matrox 4Sight under Windows NT Embedded
Working Directory: Leave this field blank.
Remote Executable Path: Specify the name and path of
the executable file so that the target computer can locate it.
6. From the command prompt on the target computer, run the
remote debug monitor MSVCMON. In the Visual C++
Debug Monitor window, click on the Settings button. The
Settings dialog box is presented. Enter the development
computer's computer name in the Target machine name
edit field. In the Visual C++ Debug Monitor window, click
on the Connect button to start the connection.
7. On the development computer, select Debugger Remote
Connection from the Build menu. The Remote
Connection dialog box is presented. Select Network
(TCP/IP) as the connection method, and then click on the
Settings button. In the Target machine name edit field
of the presented dialog, enter the target Matrox 4Sight
unit's computer name (do not use backslashes in the
machine's name).
8. Click OK and start debugging as usual.
9. When Visual C++ tries to access the symbolic information
of the DLLs that are used by your application, Visual C++
will ask you to enter the location of the dependent DLLs if
they are not on your development computer. Visual C++
may have difficulty locating the proper DLLs if the service
packs differ from Matrox 4Sight to the development
computer. The Find Local Module dialog box (which will
appear automatically) allows you enter this information.
Enter the full path of each DLL listed in the dialog; this
path must include the machine name where the shared
directory is located.
To ensure fast remote debugging, close any unneeded debugger
windows to minimize the amount of information that must be
sent across the connection. Also, minimize the use of data
breakpoints.
Hide quick links:
Advertisement
Table of Contents
