There are several commands for starting a debugger under GUD, each corresponding to a particular debugger program.
gud-xdb-directoriesto specify directories to search for source files.
Some versions of SDB do not mention source file names in their
messages. When you use them, you need to have a valid tags table
(see Tags) in order for GUD to find functions in the source code.
If you have not visited a tags table or the tags table doesn't list
one of the functions, you get a message saying ‘The sdb support
requires a valid tags table to work’. If this happens, generate a
valid tags table in the working directory and try again.
Each of these commands takes one argument: a command line to invoke the debugger. In the simplest case, specify just the name of the executable file you want to debug. You may also use options that the debugger supports. However, shell wildcards and variables are not allowed. GUD assumes that the first argument not starting with a ‘-’ is the executable file name.
Tramp provides a facility to debug programs on remote hosts (seeblog comments powered by ), whereby both the debugger and the program being debugged are on the same remote host. This should not be confused with debugging programs remotely, where the program and the debugger run on different machines, as can be done using the GDB remote debugging feature, for example (see ). Disqus