Abstract:
A method and apparatus for debugging computer programs without recompiling them is disclosed. Marcos which may be called on to expand into operable code are inserted in the program at various locations. The programmer may select or deselect the macros from the command line and run the program repeatedly without recompiling the program for different tests. Marcos may also be deselected permanently and reversibly by recompiling with the marcos undefined so that they expand to empty code. Argument processing code and symbol table code are provided to control and track the debugging procedure.

Description:
BACKGROUND OF THE INVENTION 
     1. Field of the Invention 
     The invention is directed to a method and apparatus useful for debugging computer programs and in particular to a method which allows selective tracking of the program by means of command line arguments without the necessity of recompiling the program. 
     2. Prior Art 
     When a new computer software product is conceived, there is a typical cycle or process that takes place in the course of bringing the product to the market. The programming cycle typically includes the conception of the idea; design of the software to implement the idea; coding of the program based on the system design; initial testing in the development environment; testing at the user site; and final release of the software to the market. 
     For example, after an idea occurs for a software product, system design takes place. This includes choosing the language, the compiler and the debugger to use for the product. Thereafter the programmer codes the program based upon the system design. Testing at the development side and in the user environment assures that the program will work as designed. If successful the product is released. 
     Normally the release of a software product depends on meeting development deadlines. If defects or errors (known as bugs) appear in the code, the product deadline will be missed. This is particularly likely if the bugs are complex, subtle or otherwise difficult to find. Such delays can cause a software product to fail in the marketplace. The present invention provides a debugging tool as a means for meeting deadlines as well as a meand for creating software that goes to market relatively free of errors. 
     There are many problems with existing debugging software tools. For example, programs are often debugged through the use of print statements which the programmer inserts throughout the program being debugged. When a problem occurs in a program, the programmer inserts the print statements in essentially a hit and miss way in order to try to locate the error. There are several serious problems with this approach. 
     When the program first fails, there are normally no print statements in the code that would indicate to the programmer where to look for the error. Thus the programmer must either use some separate method to find the general location of the error, or scatter print statements at random throughout the program in the hope that at least one print statement will provide some clues about where the problem lies. Of course, the more subtle the problem, the less likely the programmer is to choose the proper location for a print statement on the first try. Therefore, at the outset, at least, the programmer has no logical place to start the dubugging process. 
     In order to collect a significant amount of data from which to look for symptoms of the error, the programmer must insert a large number of print statements after the error has occurred. A great deal of time may be spent creating these statements. 
     Certain kinds of errors change their behavior depending upon the precise location and code. These errors destroy parts of the object code which strongly effects how the errors manifest themselves. For these kinds of errors, inserting print statements may change the nature of the error or even make it seem that the error has disappeared. When the print statements are removed, the error reappears. This kind of error can be extremely frustrating to a programmer trying to track down the ultimate cause of the bug. 
     The more print statements a programmer uses, the more output is generated. As frequently happens, so much output is generated that any significant information is buried in a mass of unimportant details. Thus, the programmer must always guess whether the benefits of inserting a print statement outweigh the disadvantages of creating unhelpful output. 
     Inserting print statements requires that all or part of the program be recompiled and relinked which is again a time consuming process. Likewise, when the programmer decides to remove a print statement, the program must be recompiled and relinked again. This also takes time. Once the print statement is removed it may not be reinserted without recompiling. Thus, each insertion or deletion of a print statement requires significant time and effort. 
     Because of the time required to insert and delete print statements, programmers are reluctant to experiment with output. The programmer is always asking whether the information obtained with a print statement is worth the time involved in inserting and removing the print statement. 
     It is difficult to keep track of what print statements were used in previous debugging runs. There is no obvious record of print statements that the programmer inserted or removed from one test run to another. This makes it difficult to reproduce and evaluate previous experiments. 
     When the programmer finds the cause of a bug, the print statements which were inserted must be removed or else they may hide or obscure operation of the program. The programmer must also repeat the entire cycle for each bug encountered. 
     In summary then, the use of print statements in debugging is extremely time consuming and frustrating for the programmer. It discourages spontaneous experimentation during a development cycle and such experiments if attempted are difficult to reconstruct. It may be impossible to recreate the symptoms of a problem when print statements are inserted and finally all work in finding a bug is discarded once the bug is found. No matter how many bugs a programmer finds, finding the next bug is just as difficult as finding the first. No tools are ever retained, reused or built upon in a logical systematic matter. 
     SUMMARY OF THE INVENTION 
     The present invention is a method of debugging a program using machine command line arguments without the necessity of recompiling the program. The method includes the steps of preparing a plurality of macros having corresponding expandable series of source code instructions for selectively tracing the program at selected program locations. The method further includes selectively activating the macros to perform corresponding tracing operations using command line arguments. The macros may be enabled or disabled without affecting the location of program code thereby avoiding the loss of a bug as in prior arrangements. A running count of macro calls and program line executions may be incorporated into the system. 
    
    
     DESCRIPTION OF THE DRAWINGS 
     FIG. 1 is a schematic representation in block form illustrating the arrangement and architecture of the present invention. 
     FIG. 2 is a schematic representation in block form of a detail of the present invention. 
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT 
     The invention is directed to a method of debugging a program. It may be best implemented by a computer program which is compiled and linked with the main program to be debugged to create a composite program under test. The debugging program of the invention becomes part of the main program as it performs trace operations. Except for slowing down the main program at those locations where a trace is implemented, the debugging program does not significantly interfere with the main program. On the other hand, a trace may be disabled without rearranging code in memory thereby avoiding problems of coding errors due to the presence or absence of trace statements. When trace statements are selectively disabled, the program may be run at near normal speed to check its operation quickly. 
     Definition of Terms 
     Before proceeding further with the description of the invention, certain words shall be briefly described in order to assist in the understanding of the invention. These definitions should not be construed as all encompassing or limiting. The terms are generally known to those skilled in the art and may take on different meanings dependent upon how used. In general, however, the definitions accurately describe the terms for purposes of this discussion. 
     Bug: Any defect in a computer program. 
     Command Line: The instructions used to start a program. A command line may contain command line arguments used to modify the way in which the program will work. 
     Compile: To translate from source code to object code. 
     Compiler: A computer program which translates the source code of another program into object code. 
     Debug: To remove bugs from the source code of a computer program. 
     Dump: A display of the contents of the memory of a computer at a particular instant in time. 
     Function: A portion of a computer program which acts as an independent unit. 
     Linker: A program which gathers object code together to produce a computer program. 
     Macro: A definition, created by the computer programmer, of an abbreviation to be used throughout a computer program. 
     Macro Call: An appearance in the source code of an abbreviation defined by a macro. The macro is &#34;expanded&#34; by substituting into the source code the next full text of which the macro is an abbreviation. 
     Object Code: The form of a computer program created by a compiler. The form of a computer program which may be executed by the computer directly. 
     Output: The result of a computer program which may appear either on the terminal of the computer or on some other medium. 
     Print Statement: An instruction to the computer which causes output of some kind. 
     Routine: Synonym of function. 
     Source Code: The form of the computer program created by the computer programmer. The humanreadable form of a computer program. 
     Symbol Table Code: A set of routines which store and return information about a particular class of computer objects. 
     Tool: Any computer program or routine which makes computer programming easier. 
     Trace: A record of the sequence or execution of a computer program. 
     Specific Discussion of the Invention 
     The invention may be described with respect to FIG. 1 as a method of debugging a main program 10 using a debugging program having three major portions as follows. 
     (I) A set of macros 12. Macros as noted above are definitions of abbreviations used throughout the program. When called, macros 12 are expanded to full source text prior to translating the source text into machine code. In other words, when a call for a macro 12 is encountered by the compiler the source code represented by the macro is incorporated into the program at that point. In general, in the present invention macros trace programs and count the occurrence of routines as hereinafter shown in detail. Source code for expanded macros is listed in the Appendix attached hereto. 
     The macros 12 allow the programmer to quickly specify with great precision actions in an abbreviated format. More importantly, the programmer may disable all the debugging macros in a file by simply setting one switch and recompiling the file as hereinafter described. The macros 12 are defined in a header file which is included in all of the files to be tested. 
     (II) Symbol table code 14 or a set of programs for handling (storing and returning) information about certain computer objects or symbols. The table allows the expanded macros to determine whether tracing has been enabled for a particular symbol. The symbol table code 14 also allows statistics to be kept for each symbol, whether or not tracing has been enabled for it. The Appendix lists the source code for these programs. 
     (III) Initialization code 16 or a computer code for enabling or disabling symbols from the command line. This computer code must appear in the beginning of the program under test. The code allows the programmer to insert and delete command line arguments which are executed by the programmer. The Appendix lists the source code for these programs. 
     Operation of the Program 
     Referring to FIG. 1, the invention operates as follows: 
     The main program 10, the set of macros 12 and the initialization code 16 may be combined in one file 18. The program 10 to be debugged is compiled or preprocessed on compiler 20 with the macros 12 of the debugging program to produce a program link module 21 (PLM). The main program includes a header file 10&#39; which includes therein a definition of terms. The header file 10&#39; places in a central and universal location the definition of a term or terms which will be used often in a program. Header files are house keeping devices. In the present invention the header file includes the definition of the symbol called BUG which is hereinafter described. 
     The PLM 21 is linked using a linker 22 with a symbol table code 14 (debugging module) to produce a runnable program 24 or program under test (PUT). Thereafter, command line arguments 32 are input in the PUT 24 to produce trace outputs 26 and statistics 28 as well as the normal output of the PUT 29. 
     Macros 12 shown in FIG. 2 have a definition 30 consisting of two sub definitions: the first one is used when the symbol BUG is defined and a second is used when the symbol BUG is not defined. The said definition 30 is incorporated into the program under test 24. Command 32&#39; may be used to choose between the two sub definitions of the main definition. When the symbol BUG is defined, the definition 30 of the macro 12 expands to code 36. When the symbol BUG is not defined, macro 12 expands to empty code 38. The runnable code 36 becomes part of the PUT 24 and is executed. Empty code 38 is essentially ignored. 
     After debugging, macros 12 may be permanently deselected or undefined and removed from the source code. This occurs because if a macro 12 is undefined and the program encounters a macro call which has no corresponding definition, no code is generated for the macro. In other words, the macro expands to empty code. After the macros are all deselected, the program under test 24 is recompiled to produce the program which may be marketed. 
     Table I below names and defines routines for handling the symbol table 14. These routines are called by the macro calls and expand source code when defined or expand to zero when undefined. 
     
                       TABLE I______________________________________Table Handling Routines______________________________________bug --dump ( ):        Dump all statistics that have been        gathered.bug --init ( ):        Initialize the statistics gathering module.bug --on     Enable the tracing of string.(string):bug --off    Disable the tracing of string.(string):bug --tick   Increment the statistics associated with(string):    string.bug --ton ( ):        Enable all tracing.bug --troff ( ):        Disable all tracing.bug --trace  Return TRUE if tracing is enabled for(string):    string.______________________________________ 
    
     Except for bug --  unit (), bug --  on (), and bug --  off (), which are used by the main routine to turn tracing on and off, these routines should not be called directly because that would make it tedious to remove them when debugging is complete. Instead, the macros corresponding to these routines are used. In this way, removing all debugging statements is relatively simple. The definition of BUG is removed from the header file and all files are recompiled. 
     The following macro calls listed in Table II are available to call on the routines of Table I. 
     
                       TABLE II______________________________________Macro Calls______________________________________BUG --DUMP ( ):        Dump all statistics that have been        gathered.BUG --INIT ( ):        Initialize the statistics gathering        module.BEGIN --TRACE        Enable tracing of string.(string):END --TRACE  Disable tracing of string.(string):TICK         Increment the statistics associated with(string):    string.TRON         Enable all tracing if we had been(string):    tracing string before tracing was        disabled.TROFF:       Disable all tracing.TRACE        Execute statement list if tracing string.(string,statementlist):Disabling tracing using TROFF or bug --troff speeds theexecution a great deal; a factor of 10-20 is not uncommon.______________________________________ 
    
     There is one special string understood by the debugging routines. The call of bug --  on (&#34;trace&#34;) is equivalent to bug --  ton (&#34;*&#34;) and the call to bug --  off (&#34;trace&#34;) is equivalent to bug --  troff(). To put it another way, the macro call BEGIN --  TRACE (&#34;trace&#34;) is equivalent to TRON (&#34;*&#34;), and the macro call END --  TRACE (&#34;trace&#34;) is equivalent to TROFF. The reason for this special convention is to turn on and off all tracing from the command line using +trace or -trace. 
     The following is a procedure of the basic steps to follow when using the debugging program of the present invention. 
     PROCEDURE 
     Step 1: Prepare Source Files. 
     Use the TICK macro at the very beginning of every subroutine of function. This macro gathers statistics about how many times the routine is called and also will print a message if tracing is enabled. 
     Using the TRACE macro whenever it is desired to have a trace of the program. Likely candidates include: 
     (1) At the start of each function to show the arguments to a function. 
     (2) At the end of each function to show the results of the function. 
     (3) In the middle of program loops to show the progress of the program. 
     (4) Before and after complicated calculations to show how those calculations proceeded. 
     For example, suppose the programmer is writing a C language function called f. The programmer would typically add the following kinds of TICK and TRACE calls: 
     
         ______________________________________int f (a, b, c)char *a;int b,c;int i, r;TICK (&#34;f&#34;); ##STR1##for (i=o; i&lt;b; i++) { ##STR2##} ##STR3##return r;}______________________________________ 
    
     It may seem that using this debugging package is illogical; after all, many macro calls must be inserted in the code. In practice though, the additional time spend in creating these TICK and TRACE macros is negligible compared with the time saved debugging. Putting in TICK and TRACE macros becomes second nature and adds only a few percent to the time required to type in programs. The small amount of time spent typing in TICK and TRACE macros probably saves several minutes in debugging time in the long run. The payoff is using these macros systematically is enormous. 
     In order to have access to all the macros, the programmer must include the header file BUG.H in all files. One way to do this without changing all source files is to include BUG.H in the master header file 10&#39;. 
     The symbol called BUG must be defined in every file in which the TICK and TRACE macros are used. If BUG is not defined, the TICK and TRACE macros generate absolutely no code. 
     Step 2: ADD Argument Processing Code to Program and Test. 
     The program must be able to translate command line arguments of the form: 
     
         +routine or 
    
     
         -routine 
    
     into calls on the bug --  on () and bug --  off () routines. For example, if the program were called p and you invoked p as follows: 
     
         p+abc in out 
    
     then the program would have to call bug on (&#34;abc&#34;); this process is not very difficult. Examples of how to process command line arguments are included with the debugging package. 
     Step 3: Run the Program with Appropriate Command Line Arguments from a Submit File. 
     For a variety of reasons the programmer will probably want to invoke the program from some kind of batch file (also known as a shell file or submit file). This saves the programmer from retyping long command lines and also serves as a permanent record of exactly what tests were run on the program. A record of previous runs may be prepared by leaving them in the batch file, but commenting them out so that only one version of the test is &#34;active&#34; in the batch file at any one time. 
     For example, suppose a program called p is usually called with two arguments as follows: 
     
         p in out 
    
     If the programmer wants to turn on the tracing for the routine called abc, the following command line argument may be typed: 
     
         p+abc in out 
    
     Wildcards can be used in the names of the routines to trace. For example, to turn on tracing of all routines starting with &#34;abc&#34;, but not the routine called &#34;abc1&#34; the following may be written on the command line: 
     
         p+abc*-abc1 in out 
    
     The asterisk (*) matches 0 or more characters. A question mark matches exactly one character. 
     The debugging routines treat the string &#34;trace&#34; in a special way. 
     
         -trace turns off all tracing until enabled by a TRON macro call 
    
     Step 4: Eliminate Tracing Code as Needed. 
     When tracing is no longer desired for the routines in a particular file, the programmer undefines the symbol called BUG and recompiles the entire file. All the debugging code is thereby eliminated. There is no need to actually remove the TICK and TRACE macros from the files; in fact, it would be a mistake to do so because they may be needed again if further debugging becomes necessary. 
     Typically, recompiling with BUG undefined would be done only for when the debugged code is being prepared for release--compiling out the debugging macros makes it impossible to do further tracing. Of course, when further bugs are found, tracing can be done in one of two ways: (1) an archive copy of the program with tracing still in can be used; or (2) the appropriate sections of code can be recompiled with BUG turned on again. 
     Below is a brief summary of the debugging process: 
     I. Prepare Source Files 
     A. Include header file BUG.H 
     B. Include TICK and TRACE macros 
     C. Add argument processing code 
     D. Add Symbol Table Code (Debugging Routine) 
     II. Create program under test 
     A. Compile all parts of the program 
     B. Compile the debugging routines 
     C. Link the debugging routines with the program 
     III. Run program under test 
     A. Create batch file 
     B. Enable appropriate traces 
     C. Run program 
     D. Examine the output created by the TICK and TRACE macros. 
     IV. Prepare program without tracing 
     A. Recompile with definition of BUG deselected 
     (NOTE: Step IV may be reversed to select BUG and combined with a recompile step so that further debugging may be accomplished if desired.) 
     The macros are inserted where appropriate in the main program. For example, TICK (&#34;abc&#34;) will cause an entry to be created in the symbol table created by the symbol table code 14 each time routine abc is accessed. The TICK macro also counts the number of times it has been called with a particular string as to argument. TRACE (&#34;abc&#34;) will trace the routine called abc each time it occurs. By using wild card definitions and minus statements portions of abc may be omitted from the TRACE statement. Also TRACE statement can be written so that a TRACE occurs only after a certain number of occurrences (TICKs). This is often used in a situation where the program runs properly for a long time and then all of a sudden a bug appears. Such an instruction allows the program to turn at practically full speed until it is supposed that the error is likely to occur after which TRACE statements are executed. 
     TRACE macros may be selectively disabled or deselected from the command line in order to simplify or reduce output. In other words only certain routines may be traced so that experiments may be performed. Also all traces may be disabled from the command line using the -trace option. Running the program with such an option in the command line causes the PUT to run at almost full speed. A variety of other arrangements may be attempted by those skilled in the art. 
     In the present invention the argument processing code allows enabling or disabling of TICKs and TRACEs from the command line directly. Thus, tracing with the present invention may be accomplished without recompiling the program each time the program is run with a new set of TRACE statements. Also, all TRACE and TICK statements may be permanently but reversibly deselected by means of changing the header file definition and then recompiling the program after it has been debugged. 
     The present invention allows selective use of TRACE and TICK statements without causing the program to move code to different memory locations each time a TICK or TRACE is selectively enabled or disabled. Thus problems associated with the destruction of object code as occurs in the prior art is obviated. ##SPC1##