Dbx 1024 User's Guide download pdf (Page 44)

Chapter 4: Controlling dbx

For example, to stop recording session 4, enter the dbx command:

(dbx) unrecord 4

To stop all recording sessions, enter:

(dbx) unrecord all

The dbx status command does not report on recording sessions. To see

whether or not any active recording sessions exist, use the record command

described in “Examining the Record State” on page 31.

Playing Back Input

Use playback input to execute commands that you recorded with the record

input command. Two aliases exist for playback input: pi and source.) If you

don’t specify a ﬁlename, dbx uses the current temporary ﬁle that it created

for the record input command. If you set thedbx variable $pimode to nonzero,

the commands are printed out as they are played back. By default, $pimode

is set to zero.

Recording Output

Use the record output command to start output recording sessions within dbx.

During an output recording session, dbx copies its screen output to a ﬁle. If

the speciﬁed ﬁle already exists,dbx appends to the existing ﬁle. You can start

and run as many simultaneous dbx output recording sessions as you need.

By default, the commands you enter are not copied to the output ﬁle;

however, if you set the dbx variable $rimode to a nonzero value, dbx also

copies the commands you enter.

Each recording session is assigned a number when you begin it. Use this

number to reference the recording session with the unrecord command

described in “Ending a Recording Session” on page 29.

Therecord output command is very useful when the screen output is too large

for a single screen (for example, printing a large structure). Within dbx, you

can use the playback output command (described in “Playing Back Output”

on page 31) to look at the recorded information. After quitting dbx, you can

1 2 ... 39 40 41 42 43 44 45 46 47 48 49 ... 157 158

No comments

Dbx 1024 User's Guide Page 44