Design and Implementation of a Documentation Tool for ... - MADOC

A new PTY master is requested like this:
29a 〈open new pseudo terminal 28e〉+≡ (7b) ⊳ 28e 29b ⊲
if ((PTM = posix_openpt(O_RDWR)) < 0) {
perror("openpt");
die("openpt failed", 0);
}
Uses die 23b and PTM 28c.
Then, access to the slave is granted.
29b 〈open new pseudo terminal 28e〉+≡ (7b) ⊳ 29a 29c ⊲
if (grantpt(PTM) < 0) {
perror("grantpt");
die("grantpt failed", 0);
}
if (unlockpt(PTM) < 0) {
perror("unlockpt");
die("unlockpt failed", 0);
}
Uses die 23b and PTM 28c.
The slaves device file name is requested using ptsname(). Since the name
is not needed during further execution, the slave will be opened and its file
descriptor stored.
29c 〈open new pseudo terminal 28e〉+≡ (7b) ⊳ 29b 29d ⊲
{ char *pts = NULL;
if ((pts = ptsname(PTM)) != NULL) {
if ((PTS = open(pts, O_RDWR)) < 0) {
perror(pts);
die("pts open failed", 0);
}
} else {
perror("ptsname");
die("ptsname failed", 0);
}
}
Uses die 23b and PTM 28c.
The parent terminal will be configured into a raw mode of operation. script
does this by calling cfmakeraw(), which is a nonstandard BSD function. For
portability reasons forscript sets the corresponding bits manually, thereby
emulating cfmakeraw(). The list of settings is taken from the termios(3) Linux
man page [3] and should be equivalent. Afterwards, the settings of the terminal
forscript was started in will be copied to the new terminal. This means that
in the eyes of the user the terminals behavior will not change, but forscript
can now document the terminals data stream with maximum accuracy.
29d 〈open new pseudo terminal 28e〉+≡ (7b) ⊳ 29c
{
struct termios rtt = TT;
29