Next: Commonly Seen Problems, Previous: Debugging Tools, Up: How to solve problems [Contents][Index]

### 13.2 Various hints on debugging

- How to find the IP address of a keyserver

  If a round robin URL of is used for a keyserver (e.g. subkeys.gnupg.org); it is not easy to see what server is actually used. Using the keyserver debug option as in

       gpg --keyserver-options debug=1 -v --refresh-key 1E42B367

  is thus often helpful. Note that the actual output depends on the backend and may change from release to release.

- Logging on WindowsCE

  For development, the best logging method on WindowsCE is the use of remote debugging using a log file name of `tcp://<ip-addr>:<port>`. The command `watchgnupg` may be used on the remote host to listen on the given port (see option watchgnupg --tcp). For in the field tests it is better to make use of the logging facility provided by the `gpgcedev` driver (part of libassuan); this is enabled by using a log file name of `GPG2:` (see option --log-file).