7.1.2 Starting the debugging server

Whenever you try to invoke the program on the remote machine, Functional Developer expects to be able to talk to the debugging server application on the remote machine. If this server is not running on the remote machine, it is not possible to run the Dylan program there either.

The debugging server must be started manually on the remote machine itself, so it is worth installing it there. (See Section 7.1.1 for information about using the debugging server installer.) Of course, if the remote machine already has the Functional Developer Enterprise Edition installed on it, you do not need to install the debugging server.

To start the debugging server choose Start > Programs > Functional Developer > Start Debug Server. You can also invoke it with debugger-server.exe, which is available in the Bin subfolder of the Functional Developer installation folder.

If the debugging server starts up correctly, a Functional Developer Debugger Server window opens. The window provides up-to-date information about active local debugger processes and remote connections. The upper pane of the window shows all locally running processes being debugged on remote machines, and the lower pane shows the remote machines that are connected to the server. A status bar at the bottom of the window displays a summary.

You can set (and later change) a password for the debugging server by using the Change Password button on the Debugger Server window. The password can be anything. By default, no password is required.

To exit the Debugging Server, click the Exit button or simply close the window.

At this point, you can return to the machine running the Functional Developer IDE, where you will be ready to run Dylan programs remotely.

---

Getting Started with Functional Developer - 31 MAR 2000