JPH04153743A - Display system for module call information - Google Patents

Abstract

PURPOSE:To improve the debugging jog efficient by providing a call information retrieval/display means in order to input a debug command at an optional part of a user program and to display the call information on an optional module. CONSTITUTION:A user inputs a debug command from a terminal equipment 10 for display of the call information. Then a call information retrieval/display means 4 is called out by a main control means 9 and checks whether the information on the module designated by the debug command is stored in a call information store table 6 or not. If so, the module, the call address contained in the table 6, and the calling frequency of each call address are displayed on the equipment 10 and an SYSOUT file 11. As a result, the calling frequency is known and the debugging job efficiency of a user program is improved.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a method for displaying module call information during debugging of a user program in an information processing system capable of generating an interrupt at the entrance of a module.

[Conventional technology]

Conventionally, in order to obtain module call information in a user program, there has been a method of interrupting execution at the module of interest and tracing the stack to obtain information such as the address and parameters of the calling module.

[Problem to be solved by the invention]

In the conventional method described above, if you want to know how many times a module in a user program has been called by which module, you can use it by setting a break point in the module in the user program using a debugger and running it continuously. Since the user must count the number of times the user has reached the called module, debugging takes time if the user makes a mistake or the number of times the module is reached is large.
The problem was that it was inefficient.

[Means to solve the problem]

The module call information display method of the present invention uses a debugger including an interrupt instruction processing means and a command input means, and a module called by a CALL statement in a user program to display the number of times the module has been called and the number of times the module has been called. It has a call information storage means for storing modules, and a call information search/display means for searching and displaying the call information in response to a request from a user.

[For production]

According to the present invention, the number of times a module is called is automatically measured and can be displayed arbitrarily, so that there is no need for the user to perform measurement work.

〔Example〕

Next, the present invention will be explained with reference to the drawings.

FIG. 1 is a diagram showing the configuration of the present invention. Further, FIG. 2 is a diagram showing the flow of operation of the present invention.

In FIG. 1, 1 is a module call information display method, 2 is an operating system, 3 is a conventional debugger, 4 is a call information search/display means, 5 is a call information storage means, 6 is a call information storage table, and 7 is a call information storage table. Interrupt command processing means, 8 command input means, 9 main control means, 10 terminal device, 11 5YSOUT file, 1
2 is a user program.

The module call information display method 1 includes a conventional debugger 3, a call information search/display means 4, a call information storage means 5, and a call information storage table 6.

When a user instructs the present invention to obtain module call details from the terminal device 10, the system is instructed to generate an interrupt at the entrance of each module in the user program 12.

Thereafter, when the user instructs to start execution of the user program 12, the execution of the user program 12 is started.

When an interrupt occurs at the entrance of a module, the interrupt instruction processing means 7 is called by the system and passes control to the main control means 9.

The call information storage means 5 is called by the main control means 9, checks whether the call address already exists in the call information storage table 6, and if it does not exist, calls the call address and the number of calls from the call address. The information is stored in the information storage table 6. If the call address exists in the call information storage table 6, the number of calls is incremented (added).

The call information search/display means 4 is called by the main control means 9, searches the call information storage table 6, edits the call address of the module to be searched and the number of calls at each address, and displays the terminal device 10 and the 5YSOUT file. Output to 11.

The command input means 8 is called from the main control means 9,
A debug command is input from the terminal device 10.

Next, the flow of operation of the present invention will be explained using FIG.

When a user program is executed and an interrupt occurs in a CALL statement, control is passed to module call information display method 1. (Step 201) Interrupt instruction processing means 7
checks whether the generated interrupt is a CALL statement interrupt, and if so, moves to step 203. CAL
If the interrupt is not an L statement, control is transferred to the conventional debugger 3.

(Step 202) The call information storage means 5 is called by the main control means 9, and it is checked in step 201 whether the address of the module in which the interrupt occurred is stored in the call information storage table 6. (Step call information storage table 6
If the information about the called module is not stored in the calling information storage table 6, the address of the module where the interrupt occurred, the calling address of the module, and the number of calls at the address are stored in the calling information storage table 6. (
Step 204) If the information of the module in which the interrupt occurred is stored in the call information storage table 6, it is checked whether the call address of the module has already been stored. (Step 205) If the call address is not already stored in the call information storage table 6, the call address and the number of calls are stored in the call information storage table 6. (Step 206) If the pop-up address is already stored in the call information storage table G, the number of calls from this address is incremented (added).

(Stentub 207) Next, the operation after inputting the debug command will be explained with reference to FIG.

The user inputs a debug command to display call information from the terminal device 1o.

(Step 301) The call information search/display means 4 is called by the main control means 9, and checks whether the information of the module specified in the debug command is stored in the call information storage table 6 (Step 302) If the module information is stored in the call information storage table 6, the module, its call address in the call information storage table 6, and the number of calls at each call address are stored in the terminal device 10 or the 5YSOUT file 11. to be displayed. (Step 303) If the error message is not stored, the error message is sent to the terminal device 10 or 5YSOU.
It is displayed on the T-file 11.

(Step 304) [Effects of the Invention] As explained above, the present invention makes it possible to know from where and how many times an arbitrary module has been called up to the present time at an arbitrary point when executing a user program. You can also check for modules that are not on the stack, which could not be checked in the past, and
You can also see the number of times it has been called.

Therefore, it is effective in improving the efficiency of debugging user programs.

[Brief explanation of drawings]

FIG. 1 is a diagram showing the configuration of the present invention. FIGS. 2 and 3 are diagrams showing the flow of operation of the present invention. ■...Module call information display method, 2...
Operating system, 3... conventional debugger,
4... Call information search/display means, 5... Call information storage means, 6... Call information storage table,
7... Interrupt command processing means, 8... Command input means, 9... Main control means, 10... Terminal device, 11.
-・5YSOUT file, 12...User program. Agent Patent Attorney Yoshihiro Yamashita Figure 2 Figure 3

Claims (1)

[Claims] In a system that can generate an interrupt at the entrance of a module, a debugger including an interrupt instruction processing means, a command input means, and a CAL
A call information storage means for storing the number of times the module has been called and the module that called the module for a module called by the L sentence, and a caller that searches and displays the call information in response to a request from a user. 1. A module call information display method, comprising: an information search/display means, and displays call information of an arbitrary module by inputting a debug command at an arbitrary location in the user program.