Intel XENIX 286 Programmers Guide (86) - Tenox.tc
Intel XENIX 286 Programmers Guide (86) - Tenox.tc Intel XENIX 286 Programmers Guide (86) - Tenox.tc
XENIX Programming Programming Commands ad b (continued) [?/]M segnum fpos size Creates a new segment in the memory map. The segment is given a file position fpos and physical size size. segnum must not already exist in the memory map. If ? is given, a text segment is created; if I is given, a data segment is created. >name dot is assigned to the variable or register named. A shell is called to read the rest of the line following !. $modifier Miscellaneous commands. The available modifiers are: f Send output to the file f, which is created if it does not exist. r Print the general registers and the instruction addressed by ip. dot is set to ip. f Print the floating registers in single or double length. b Print all breakpoints and their associated counts and commands. c C stack backtrace. If address is given, then it is taken as the address of the current frame (instead of bp}. If C is used, then the names and (16-bit) values of all automatic and static variables are printed for each active function. If count is given, then only the first count frames are printed. e The names and values of external variables are printed. w Set the page width for output to address (default 80). s Set the limit for symbol matches to address (default 255). o Sets input and output default format to octal. d Sets input and output default format to decimal. x Sets input and output default format to hexadecimal. q Exit from adb. v Print all nonzero variables in octal. m Print the address map. B-7
Programming Commands XENIX Programming ad b (continued) :modifier Manage a subprocess. Available modifiers are B-8 brc Set breakpoint at address. The breakpoint is executed count-1 times before causing a stop. Each time the breakpoint is encountered the command c is executed. If this command sets dot to zero, then the breakpoint causes a stop. dl Delete breakpoint at address. r[ arguments ] Run objfil as a subprocess. If address is given explicitly, then the program is entered at this point; otherwise, the program is entered at its standard entry point. count specifies how many breakpoints are to be ignored before stopping. Arguments to the subprocess may be supplied on the same line as the command. An argument starting with < or > causes the standard input or output to be established for the command. All signals are turned on upon entry to the subprocess. R[ arguments ] Same as the r command except that arguments are passed through a shell before being passed to the program. This means shell metacharacters can be used in file names. cos The subprocess is continued and signal § is passed to it. (See the entry for signal in "System Functions" in the XENIX 286 C Library Guide.) If address is given, then the subprocess is continued at this address. If no signal is specified, then the signal that caused the subprocess to stop is sent. Breakpoint skipping is the same as for r. ss Same as c except that the subprocess is single-stepped count times. If there is no current subprocess then objfil is run as a subprocess as for r. In this case, no signal can be sent; the remainder of the line is treated as arguments to the subprocess. k The current subprocess, if any, is terminated.
- Page 222 and 223: XENIX Programming yacc: Compiler-Co
- Page 224 and 225: XENIX Programming yacc: Compiler-Co
- Page 226 and 227: XENIX Programming yacc: Compiler-Co
- Page 228 and 229: XENIX Programming yacc: Compiler-Co
- Page 230 and 231: XENIX Programming yacc: Compiler-Co
- Page 232 and 233: XENIX Programming yacc: Compiler-Co
- Page 234 and 235: XENIX Programming yacc: Compiler-Co
- Page 236 and 237: XENIX Programming %left %left %left
- Page 238 and 239: XENIX Programming I* lexical analys
- Page 240: XENIX Programming yacc: Compiler-Co
- Page 243 and 244: m4: Macro Processor XENIX Programmi
- Page 245 and 246: m4: Macro Processor XENIX Programmi
- Page 247 and 248: m4: Macro Processor XENIX Programm
- Page 249 and 250: m4: Macro Processor XENIX Programmi
- Page 251 and 252: m4: Macro Processor XENIX Programmi
- Page 253 and 254: C Language Portability XENIX Progra
- Page 255 and 256: C Language Portability XENIX Progra
- Page 257 and 258: C Language Portability XENIX Progra
- Page 259 and 260: C Language Portability XENIX Progra
- Page 261 and 262: C Language Portability XENIX Progra
- Page 263 and 264: C Language Portability XENIX Progra
- Page 266 and 267: APPENDIX B PROG RAMMING COMMANDS Th
- Page 268 and 269: XENIX Programming ad b (continued)
- Page 270 and 271: XENIX Programming Programming Comma
- Page 274 and 275: XENIX Programming Programming Comma
- Page 276 and 277: XENIX Programming Programming Comma
- Page 278 and 279: XENIX Programming Programming Comma
- Page 280 and 281: XENIX Programming Programming Comma
- Page 282 and 283: XENIX Programming Programming Comma
- Page 284 and 285: XENIX Programming as (continued) Fi
- Page 286 and 287: XENIX Programming Programming Comma
- Page 288 and 289: XENIX Programming Programming Comma
- Page 290 and 291: XENIX Programming Programm ing Comm
- Page 292 and 293: XENIX Programming Programming Comma
- Page 294 and 295: XENIX Programming Programming Comma
- Page 296 and 297: XENIX Programming Programm ing Comm
- Page 298 and 299: XENIX Programming Programming Comma
- Page 300 and 301: XENIX Programming Programming Comma
- Page 302 and 303: XENIX Programming Programming Comma
- Page 304 and 305: XENIX Programming Programming Comma
- Page 306 and 307: XENIX Programming Programming Comma
- Page 308 and 309: XENIX Programming Programming Comma
- Page 310 and 311: XENIX Programming Programming Comma
- Page 312 and 313: XENIX Programming Programming Comma
- Page 314 and 315: XENIX Programm ing Programming Comm
- Page 316 and 317: XENIX Programming Programming Comma
- Page 318 and 319: XENIX Programming Programming Comma
- Page 320 and 321: XENIX Programming Programming Comma
Programming Commands <strong>XENIX</strong> Programming<br />
ad b (continued)<br />
:modifier<br />
Manage a subprocess. Available modifiers are<br />
B-8<br />
brc Set breakpoint at address. The breakpoint is executed count-1 times<br />
before causing a stop. Each time the breakpoint is encountered the<br />
command c is executed. If this command sets dot to zero, then the<br />
breakpoint causes a stop.<br />
dl Delete breakpoint at address.<br />
r[ arguments ]<br />
Run objfil as a subprocess. If address is given explicitly, then the program<br />
is entered at this point; otherwise, the program is entered at its standard<br />
entry point. count specifies how many breakpoints are to be ignored<br />
before stopping. Arguments to the subprocess may be supplied on the<br />
same line as the command. An argument starting with < or > causes the<br />
standard input or output to be established for the command. All signals<br />
are turned on upon entry to the subprocess.<br />
R[ arguments ]<br />
Same as the r command except that arguments are passed through a shell<br />
before being passed to the program. This means shell metacharacters can<br />
be used in file names.<br />
cos The subprocess is continued and signal § is passed to it. (See the entry for<br />
signal in "System Functions" in the <strong>XENIX</strong> <strong>2<strong>86</strong></strong> C Library <strong>Guide</strong>.) If<br />
address is given, then the subprocess is continued at this address. If no<br />
signal is specified, then the signal that caused the subprocess to stop is<br />
sent. Breakpoint skipping is the same as for r.<br />
ss Same as c except that the subprocess is single-stepped count times. If<br />
there is no current subprocess then objfil is run as a subprocess as for r. In<br />
this case, no signal can be sent; the remainder of the line is treated as<br />
arguments to the subprocess.<br />
k The current subprocess, if any, is terminated.