Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ tbx(1) — Motorola System V 88k Release 4 Version 4.2

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

cc(1)

csh(1)

kill(1)

lex(1)

make(1)

yacc(1)

tbx(1)  —  USER COMMANDS

NAME

tbx, ctbx − DeltaPRO Toolbox

SYNOPSIS

tbx [-c corefile] [-p source_path_list] [-w] [-G] [-+] [-?] [-h] [objfile]

ctbx [-c corefile] [-p source_path_list] [-w] [-G] [-+] [-?] [-h] [-I] [-C] [objfile]

DESCRIPTION

tbx is a utility for source-level debugging and execution of programs written in C, Fortran, and C++.  ctbx accepts the same commands as tbx, but uses the curses tty interface. 

objfile is an executable object file produced by cc, f77, or CC (the C++ compiler).  For full debugging capabilities, the -g option should be specified for all compilations. 

If no objfile is specified, a.out will be the default.  If the object file cannot be found, a usage message is printed. 

Each time you start a debugging session, tbx looks for a file named .tbxinit.  The user’s home directory is searched first.  If the file is not found, the current working directory is then searched.  If a .tbxinit file can be found, all commands in the file will be executed prior to the start of tbx. 

After you have started tbx, you can pass arguments to the program you are debugging by using the run command.  For details, see the online help text for run. 

OPTIONS

-c corefile Specify an alternate core file.  The default is core.  Use -c none to ignore an existing core file.  To use a core file called none, use -c ./none. 

-p source_path_list
Add source_path_list to the search path for source files.  source_path_list can be a single path or a list of paths separated by colons.  On System V Release 4, tbx will normally find source files, regardless of their location, because of path information generated by the DeltaPRO compilers.  Therefore, this option is normally only needed on System V Release 3 systems unless source files have been moved since compilation. 

-w Toggle warning reports. This includes various problems that tbx finds, primarily during the startup procedure.  If warnings are enabled, tbx also shows the name of each source file as it finds it during startup.  By default, warnings are enabled. 

-G Toggle Fortran END or ERR goto interception.  When debugging Fortran programs compiled by the DeltaPRO Fortran compiler, tbx will intercept execution of Fortran ERR= or END= I/O specifiers and report that program control was transferred abnormally.  If you do not want this to occur, specify the -G option.  If you are debugging a C program or a Fortran program compiled with a different compiler, this option has no effect. 

-+ Use C++ name demangling. 

-? Print usage information. 

-h Print usage information. 

-I Toggle terminal I/O intercept (ctbx only).  When you are using ctbx, any terminal I/O performed by your program will be intercepted by the debugger by default.  If you are debugging a program which makes minimal use of terminal I/O, or debugging an attached program, you may wish to disable this feature.  If you use this feature, any terminal I/O that your program writes will overwrite the TBX display.  For attached processes, I/O will happen in the window in which the process is running. 

-C Toggle curses application mode (ctbx only).  If you are debugging an application which uses the curses library with ctbx, you need to specify this option to prevent conflicts between the tbx curses interface and your program.  Note that this option implicitly turns on the -I option.  When the tbx display is disrupted by the actions of your program, you can use the refresh command to correct the problem. 

Standard options recognized by the X Toolkit Intrinsics, such as −geometry, −fg, and −display can be used with tbx.  Refer to the X(1) manual page for a list of these options and to the X Window System User’s Guide for complete details.  These options are used only by the tbx graphical interface. 

ENVIRONMENT VARIABLES

The environment variable TBXOPTIONS can be used to toggle the default state of the flags controlled by the -w , -G , -I , and -C options.  To do this, initialize the TBXOPTIONS variable to contain the option flags.  For example, to have tbx not report warnings and not intercept END and ERR gotos, you could specify the following command (from ksh):

export TBXOPTIONS="-w -G"

If this is done, the options can still be toggled back to their original state by using the same options on the tbx command line. 

Environment variables that are used by X (such as $DISPLAY) can also be used to modify the behavior of tbx.  Refer to the X Window System User’s Guide for complete details. 

USAGE

For a detailed discussion of the .tbxinit file, the command interface, and the graphic interface refer to the tbx manual. 

FILES

core default core file

a.out default executable target program

.tbxinit local tbx initialization file

$HOME/.tbxinit user’s tbx initialization file

/usr/lib/X11/app-defaults/Tbx
X window resource file for debugging internationalized applications. This file is used when the LANG environment variable is set to a value other than C.

/usr/lib/X11/C/app-defaults/Tbx
X window resource file for debugging English applications. This file is used when the LANG environment variable is set to a value of C or is not set.

/usr/TARs/TBX a directory containing two files: list of known problems, and list of problems fixed since last release

SEE ALSO

cc(1), csh(1), kill(1), lex(1), make(1), yacc(1). 

BUGS

Refer to the files in /usr/TARs/TBX for a list of known bugs in tbx.  For on-line information about known problems in tbx, use the tbx help command for the known_bugs and release topics. 

  —  C Programming Language Utilities

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026