1. Remote Target machine
Install D:\Program files (x86) \borland\remote debugger\20, no discs copy files from the bin directory on the installed Xe6 computer
- Bccide.dll
- Bordbk200.dll
- Bordbk200N.dll
- Comp32x.dll
- DCC32200.dll
- Rmtdbg200.exe
Registering DLL files
regsvr32 bordbk200.dll
regsvr32 bordbk200N.dll
Running Rmtdbg200.exe after boot is in listening state
2. Development environment Machine
After the C++builder is directly compiled (unlike Delphi, there is a need to generate RSM and change options), generate TDS and EXE file copies to the remote target machine.
Then run > Attach to Process input target machine Ip,refresh test connectivity
Run > Load Process > Remote
Remote Path:D: \bin\project2.exe
Remote host:192.168.24.88
Parameters: No need to fill in
The Point Load button runs on the remote target machine, not on the development machine.
Add a breakpoint, the first time there is a CPU window, close to follow the source.
The Project2.exe and Project2.tds on the target machine, as on the development machine, can be configured to share the final output as the target machine path and have writable permissions.
In the future do not have to worry about the remote special environment, direct remote debugging.
Http://docwiki.embarcadero.com/RADStudio/XE6/en/Overview_of_Remote_Debugging
Http://docwiki.embarcadero.com/RADStudio/XE6/en/Installing,_Starting,_and_Stopping_the_Remote_Debug_Server
Http://docwiki.embarcadero.com/RADStudio/XE6/en/Installing_a_Debugger_on_a_Remote_Machine
C++builder XE6 Remote Debuger debugging