Supported Debuggers

When there is no conflict with command from another package like gud, there are function aliases to the names without realgud:. For example:

M-x trepan

is the same as

M-x realgud:trepan

This means gud, perldb, pdb, and jdb (among possibly others) need to have the realgud: prefix if you want the realgud to run these.

You can also attach a debugger tracking mode to an existing comint shell. Inside a shell buffer:

M-x realgud-track-mode

You will be asked for the name of a buffer. Use one of the names above without realgud-. For example,
trepan.

For gdb, in order to track source automatically, inside gdb issue:

set annotate 1

History Ring

The debugger saves marks in a history ring at the places in source buffers that you have stopped at. To move around M-up and M-down in the debugger command buffer. (The command buffer is where you enter debugger commands which is attached to the debugger process. It is some sort of comint shell.

Short-key mode

There is a "short-key" mode which can be used in source buffers which allows single-keystroke commands, like "s" for step (into). And "n" for "next" or step through.

The short-key mode makes the source read only. To get out of short-key mode, you can use the insert key. To get back in use <Ctrl-insert>.

Editor marks in source buffer

The editor uses marks in the source buffer. However if you edit the program and then restart the debugger you may need to clear these marks with

M-x loc-change-clear-buffer

Backtrace buffer

I've been working on a backtrace buffer. To get that set up, issue from a debugger command window: