(ddd.info)Debugger Communication
2.5.3 Communication with the Inferior Debugger
----------------------------------------------
The following resources control the communication with the inferior
debugger.
-- Resource: blockTTYInput (class BlockTTYInput)
Whether DDD should block when reading data from the inferior
debugger via the pseudo-tty interface. Most UNIX systems except
GNU/Linux _require_ this; set it to `on'. On GNU/Linux, set it to
`off'. The value `auto' (default) will always select the "best"
choice (that is, the best choice known to the DDD developers).
-- Resource: bufferGDBOutput (class BufferGDBOutput)
If this is `on', all output from the inferior debugger is buffered
until a debugger prompt appears. This makes it easier for DDD to
parse the output, but has the drawback that interaction with a
running debuggee in the debugger console is not possible. If
`off', output is shown as soon as it arrives, enabling
interaction, but making it harder for DDD to parse the output. If
`auto' (default), output is buffered if and only if the execution
window is open, which redirects debuggee output and thus enables
interaction. Note: Using the Execution Window, for details.
-- Resource: contInterruptDelay (class InterruptDelay)
The time (in ms) to wait before automatically interrupting a `cont'
command. DDD cannot interrupt a `cont' command immediately,
because this may disturb the status change of the process.
Default is `200'.
-- Resource: displayTimeout (class DisplayTimeout)
The time (in ms) to wait for the inferior debugger to finish a
partial display information. Default is `2000'.
-- Resource: positionTimeout (class PositionTimeout)
The time (in ms) to wait for the inferior debugger to finish a
partial position information. Default is `500'.
-- Resource: questionTimeout (class QuestionTimeout)
The time (in seconds) to wait for the inferior debugger to reply.
Default is `10'.
-- Resource: runInterruptDelay (class InterruptDelay)
The time (in ms) to wait before automatically interrupting a `run'
command. DDD cannot interrupt a `cont' command immediately,
because this may disturb process creation. Default is `2000'.
-- Resource: stopAndContinue (class StopAndContinue)
If `on' (default), debugger commands interrupt program execution,
resuming execution after the command has completed. This only
happens if the last debugger command was either a `run' or a
`continue' command. If `off', debugger commands do not interrupt
program execution.
-- Resource: synchronousDebugger (class SynchronousDebugger)
If `on', X events are not processed while the debugger is busy.
This may result in slightly better performance on single-processor
systems. Note: Options, for the `--sync-debugger' option.
-- Resource: terminateOnEOF (class TerminateOnEOF)
If `on', DDD terminates the inferior debugger when DDD detects an
EOF condition (that is, as soon as the inferior debugger closes
its output channel). This was the default behavior in DDD 2.x and
earlier. If `off' (default), DDD takes no special action.
-- Resource: useTTYCommand (class UseTTYCommand)
If `on', use the GDB `tty' command for redirecting input/output to
the separate execution window. If `off', use explicit redirection
through shell redirection operators `<' and `>'. The default is
`off' (explicit redirection), since on some systems, the `tty'
command does not work properly on some GDB versions.
automatically generated by info2www version 1.2.2.9