(ddd.info)Customizing Remote Debugging
2.4.2.1 Customizing Remote Debugging
....................................
When having the inferior debugger run on a remote host (Note: Remote
Debugging), all commands to access the inferior debugger as well as
its files must be run remotely. This is controlled by the following
resources (Note: Customizing):
-- Resource: rshCommand (class RshCommand)
The remote shell command to invoke TTY-based commands on remote
hosts. Usually, `remsh', `rsh', `ssh', or `on'.
-- Resource: listCoreCommand (class listCoreCommand)
The command to list all core files on the remote host. The string
`@MASK@' is replaced by a file filter. The default setting is:
Ddd*listCoreCommand: \
file @MASK@ | grep '.*:.*core.*' | cut -d: -f1
-- Resource: listDirCommand (class listDirCommand)
The command to list all directories on the remote host. The string
`@MASK@' is replaced by a file filter. The default setting is:
Ddd*listDirCommand: \
file @MASK@ | grep '.*:.*directory.*' | cut -d: -f1
-- Resource: listExecCommand (class listExecCommand)
The command to list all executable files on the remote host. The
string `@MASK@' is replaced by a file filter. The default setting
is:
Ddd*listExecCommand: \
file @MASK@ | grep '.*:.*exec.*' \
| grep -v '.*:.*script.*' \
| cut -d: -f1 | grep -v '.*\.o$'
-- Resource: listSourceCommand (class listSourceCommand)
The command to list all source files on the remote host. The
string `@MASK@' is replaced by a file filter. The default setting
is:
Ddd*listSourceCommand: \
file @MASK@ | grep '.*:.*text.*' | cut -d: -f1
automatically generated by info2www version 1.2.2.9