Troubleshooting Tips

Debugging executables over NFS

You can debug executables that are stored on NFS-mounted file systems. However, you cannot attach to an existing process if the executable you are running resides on an NFS-mounted file system instead of on your local machine’s file system. To work around this problem, copy the executable onto your local machine’s file system, restart the process on your local machine, run the debugger, and attach to the process.

Attaching to a process with shared libraries

If you want to attach to a running process that contains shared libraries, before you run your program, you need to run the command /usr/bin/pxdb -s enable executable_file where executable_file is the name of your program executable.

Double-Clicking with ReflectionX

If you are running the WDB GUI using ReflectionX, the default double-click parameters may be too sensitive to work properly. You can increase the double-click time by setting the following X resource:

Wdb*multiClickTime: 600

For information on setting X resources, refer to the xrdb(1) man page or to the RESOURCES section of the x(1) man page.

Setting breakpoints that never appear in the breakpoints list

You may set a breakpoint that does not show up in the breakpoints list. This may be caused by:

The breakpoint has been deferred. See Working with Deferred Breakpoints.
Or a breakpoint was actually set as you specified, however the debugger cannot locate the appropriate file using the current source file paths that you have set. To update the source file paths, see Setting Source Paths.

Problems with keyboard shortcuts or mneumonics

If you have problems with keyboard shortcuts or mneumonics, check if the CAPS LOCK or NUM LOCK key is active. These modifier keys disable most shortcut and mneumonic features. To use the short cuts and mneumonics, be sure that these two modifier keys are de-activated.