Source: Borland Developer Studio 2006 Help.
To install the remote debugger if the installation disk is not available * Create a directory on the remote machine for the installation files.
C:\Program Files\Borland\BDS\4.0\Bin
):rmtdbg100.exe
bccide.dll
bordbk100.dll
bordbk100N.dll
comp32x.dll
dbkpro100.dll
DCC100.DLL
DCC100IL.DLL
Borland.dbkasp.dll
bordbk100.dll
and bordbk100n.dll
by running the regsvr32.exe registration utility. For example, on Windows XP, enter C:\Windows\System32\regsvr32.exe bordbk100.dll
at the command prompt, then enter C:\Windows\System32\regsvr32.exe bordbk100n.dll
. Borland.dbkasp.dll
to the Install\GlobalAssemblyCache
directory on the remote machine. If you are debugging an ASP.NET application, register the Borland.dbkasp.dll
in the GlobalAssemblyCache
using the Microsoft .NET gacutil.exe
utility. For example, on Windows XP with Microsoft .NET Framework SDK, enter C:\Program Files\Microsoft.NET\SDK\v1.1\Bin\gacutil Borland.dbkasp.dll
. You must establish a TCP/IP connection between the local and remote machines in preparation for remote debugging. This connection uses multiple ports that are chosen dynamically by Windows. The remote debug server listens on one port, and a separate port is opened for each application that is being debugged. A firewall that only allows connections to the listening port will prevent the remote debugger from working.
Note: If the remote machine uses the firewall included with Windows XP service pack 2, you will receive a message asking whether Borland remote debugging service should be allowed. You must indicate that this is allowed. Warning: The connection between Developer Studio 2006 and the remote debug server is a simple TCP/IP socket, with neither encryption nor authentication support. Therefore, the remote debug server should not be run on a computer that can be accessed over the network by untrusted clients. To connect the local machine and the remote machine * Ensure that the remote debugger is installed on the remote machine.
rmtdbg100.exe
with the -listen
argument. rmtdbg100.exe -listen
This starts the remote debugger's listener and directs it to wait for a connection from your host machine's IDE.
program1.exe
, and you copy this to a directory named RemoteDebugFiles\Program1
on the remote machine, specify C:\RemoteDebugFiles\Program1\program1.exe.
Once this connection is established, you can use the IDE on the local machine to debug the application as it runs on the remote machine. Note: You cannot interact directly with the remote application through the remote debugger. For interactive debugging, you can establish a remote desktop connection.
Executable files and symbol files must be copied to the remote machine after they are compiled. You must set the correct options on your local machine in order to generate these files. To prepare files for debugging on a remote machine * Open the project on your local machine.
Language | Debug symbol file extension |
---|---|
Delphi for Win32 | .rsm |
Delphi for .NET | .rsm and .pdb |
C++ | .tds |
C# | .pdb |