TotalView User Guide : Part IV: Advanced Tools, Configuration, and Customization : Setting Up Remote Debugging Sessions : About Remote Debugging : Platform Issues when Remote Debugging
Platform Issues when Remote Debugging
In general, when debugging programs remotely, the architecture of the remote machine must be compatible with that of the machine running TotalView. For example, you cannot perform remote debugging on a 64-bit Linux system if you launch TotalView from a 32-bit Linux system. In addition, the operating systems must also be compatible.
However, TotalView supports several forms of heterogeneous debugging in which the operating system and/or architecture differ. For example, from a Linux x86-64 session, you can debug remote processes on Linux Cell.
This table shows supported combinations:
Host System
Target System
Linux x86-64
Linux x86
Linux x86-64
Linux Power 32
Linux Power 64 / Cell
Cray XT
Linux x86
Linux x86
Linux Power 32
Linux Power 64 / Cell
Linux Power 64 (including Linux Cell)
Linux Power 32
Linux Power 64 / Cell
Blue Gene
You must install TotalView for each host and target platform combination being debugged.
*The path to TotalView must be identical on the local and all remote systems so that TotalView can find the tvdsvr program.
TotalView assumes that you launch tvdsvr using rsh. If rsh is unavailable, set the TVDSVRLAUNCHCMD environment variable to the command that you use to remotely access the remote system. In most cases, this will be ssh.
*If the default single-process server launch procedure meets your needs and you’re not experiencing any problems accessing remote processes from TotalView, you probably do not need the information in this chapter. If you do experience a problem launching the server, check that the tvdsvr process is in your path.