JPH0431933A - Source program analyzing device - Google Patents

Abstract

PURPOSE:To detect an error related to the synchronizing exclusive control for an analyzing device of a source program described in a high level language by carrying out the analysis based on the event information showing the using condition of the variable emerging in the source program. CONSTITUTION:A program analyzing part 2 analyzes the program unit of a source program 10 and stores the result of this analysis in to an analysis data base 30. When the analyses of all program units are over, the control is shifted to a total program analyzing part 3. The part 3 recognizes first the program component group of the program 10 based on the information on the base 30 and adds the result of this recognition to the base 30. Then the part 3 refers to the contents of the base 30 to produce the event type information showing the using state of each event emerging in the program 10 and then detects an error related to the synchronizing exclusive control based on the event type information.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to an apparatus for analyzing a source program written in a high-level language in a computer system.

[Prior Art] Analyzing the structure of a source program written in a high-level language and detecting errors has traditionally been performed using an analysis device installed in a compiler, etc. In such primitive programs, the range of error detection is limited to errors within program units.

(Problems to be Solved by the Invention) As mentioned above, conventional source program analysis devices only detect errors within program units;
Errors that span program units, that is, errors related to synchronized exclusive control of tasks between program units, cannot be detected, and errors are often discovered only after the source program is executed.

SUMMARY OF THE INVENTION An object of the present invention is to provide an analysis device that detects errors related to synchronized exclusive control of tasks between program units by analyzing a source program.

(Means for Solving the Problems) In order to achieve the above object, the present invention has been created for a computer system having a multitasking function that divides an executable program into different tasks and executes them in parallel. A source program analysis device consisting of multiple program units written in a language inputs and analyzes each program unit of the source program, and analyzes the task-related statements that appear within the program unit for each program unit. A program unit analysis section that generates program unit information that collects information, an analysis database that stores the information generated by the program unit analysis section, and a variable for each variable that appears in the source program based on the information stored in the analysis database. An entire program analysis section that generates event type information indicating the usage status of the program and detects errors related to synchronous exclusive control based on the generated event type information, and an analysis that includes information on errors detected by the entire program analysis section. and an information output section that outputs information.

In a preferred embodiment of the present invention, in addition to generating the above-mentioned program unit information, the program unit analysis section also generates CALL statement information that collects information regarding CALL related statements for each program unit, and the program structure of the source program. The entire program analysis unit recognizes program configuration groups based on the information stored in the analysis database, and also analyzes the usage status of variables for each variable that appears in the source program. The event type information including the program configuration group is generated, and errors related to synchronous exclusive control are detected based on the generated event type information.

; Effect] In the source program analysis device of the present invention, the program unit analysis section manually analyzes each program unit of the source program, and extracts information regarding task-related statements appearing in the program unit for each program unit. Generates program unit information that collects information. At this time, in a preferred embodiment of the present invention, CALL statement information that collects information regarding CALL-related statements for each program unit and program configuration information of the source program are also generated.

The information generated by the program unit analysis section is stored in the analysis database, and then the entire program analysis section generates event type information indicating the usage status of the variable for each variable that appears in the source program based on the information stored in the analysis database. At the same time, errors related to synchronous exclusive control are detected based on the generated event type information. At this time, in a preferred embodiment of the present invention, the program configuration group is recognized based on the information stored in the analysis database, and the event type is used to indicate the usage status of the variable for each variable appearing in the source program, including the program configuration group. Generate information. Thereafter, the information output section outputs analysis information including information on the error detected by the entire program analysis section.

〔Example〕

Next, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 14 is a configuration diagram of an embodiment of the present invention. The analysis device 1 of this embodiment is a device that inputs and analyzes a source program 10 and outputs output information 20 including information on errors related to synchronized exclusive control of tasks in the source program 10. It includes a section 2, an overall program analysis section 3, and an information output section 4, and is provided with an external analysis database 30.

The source program 10 is composed of a plurality of program units written in a high-level language. 10 are executed in parallel as several tasks.

A program unit analysis section 2 in the analysis device 1 manually analyzes each program unit of the source program 10 and stores the analysis results in an analysis database 3o. When the analysis of all program units is completed, control is passed to the entire program analysis section 3. In this embodiment, the program unit analysis section 2 generates the following information.

■Program unit information that collects information about task-related statements that appear within each program unit. Here, task-related statements include task start, exclusive section start, exclusive section end, task waiting, synchronous wait start,
This refers to a statement related to a synchronization wait, etc., and the information related to a task-related statement includes the name of the nine variables used in the task-related statement, the name of the program unit on which it acts, the line number of the task-related statement, etc. .

■CALL statement information that collects information about CALL-related statements for each program unit. Here, the CALL-related statement refers to a statement related to starting a task or calling a subroutine, and the CALL statement information refers to the type of CALL statement,
The name of the program unit being called, the line number of the current 1cALL related statement, etc.

■Program configuration information of source program 10. here,
The program configuration information is information indicating what names and two types of program units the source program 10 is composed of, and the reference relationship between the program units.

The analysis database 30 shown in FIG. 11 is a storage means for holding the above-mentioned information obtained by the program unit analysis section 2. This analysis database 30 is referred to by the entire program analysis section 3.

When the entire program analysis section 3 receives control from the program unit analysis section 1, it first recognizes and recognizes the program configuration group of the source program 10 based on the information stored in the analysis database 30.

In this embodiment, the identification results are added to the program configuration information stored in the analysis database 30. Here, the program configuration group of the source program 10 is a set of program units starting with the main program unit or the program unit activated by a task, and each program unit or program unit being activated or called by a task, and has a multitasking function. In a total of X machine systems, each program configuration group is executed as one task. Next, the entire program analysis section 3 refers to the contents of the analysis database 30 and generates event type information indicating the usage status of the variable including the program configuration group for each variable that appears in the source program 104. Here, the usage event type information is information indicating what type of event each variable is used for, and in which program unit and program configuration group each variable is used. Then, the entire program analysis section 3 detects an error related to synchronous exclusive control based on the generated event type information, and passes control to the information output section 4 after the processing is completed.

The information output unit 4 outputs analysis information including information on errors detected by the entire program analysis unit 3 as output information 20 from a display device, a printer, etc. (not shown).

The above is the overall configuration and rough operation of this embodiment, but in order to further facilitate understanding of the present invention, the content of this embodiment will be explained in more detail with reference to the drawings starting from FIG. do.

First, a flowchart showing a processing example of the program unit analysis unit 2 in FIG. 2, an example of the contents of the analysis database 30 in FIG.
The configuration and operation of the program unit analysis section 2 will be explained with reference to the configuration example of the source program 10 shown in the figure.

In the example of FIG. 4, the source program 10 consists of four program units 410, 420,
It consists of 430,440 program units, 41 program units.
0 is the main program with the program unit name "MAIN", and the remaining program units 420, 430, 440
are the program unit names "5UBI" and "5UB2" respectively.
This is a subroutine program with ``,'' and ``5UB3''.

Each program unit 410, 420, 430゜440
In the line number part shown in the same figure, the first sentence, task-related sentence,
Sentences 411 to 416, 42 that are any of the CALL related sentences
1 to 424.431 to 435441 are included.

The program unit analysis unit 2 analyzes the source program 10 composed of program units 410, 420, 430, and 440 as shown in FIG. 4 by executing the processing shown in FIG. Information as shown in FIG. 3 is generated on the analysis database 30. Here, the program unit information 310, 320, 330, 3 in FIG.
40 are program units 410, 420, 430 respectively
440, and the program unit name,
Stores information about the program type and task-related statements that perform task activation and synchronous exclusive control that appear in the program unit. Further, the CALL statement information 350 and 360 are generated from the program unit 410430, respectively.
Stores information on task activation statement δ and CALL statement. Furthermore, the program configuration information 370 includes the source program 10
The name of the program units that make up the program, the type indicating whether each program unit is a main program or a subroutine, and the CA
Stores information such as reference status indicating whether it is called by a LL statement or a task is activated.

The program unit analysis section 2 inputs the program units 410, 420, 430, and 440 shown in FIG. 4 from the source program 10 in that order, and specifically performs the following processing.

First, in the process 100 of FIG.
When a statement 411 indicating the start of program 0 is input, it is recognized in process 120 that it is the first statement of the program unit 410, and the following information storage process is performed in process 130.

■ The program unit name "MAIN" in the statement 411 indicating the start of the program is stored in the program unit name 311 of the program unit information 310 as shown in FIG. Store.

■ Initially, the program unit name ``MAIN'' is not registered in any of the program unit names 372 of the program configuration information 370, so ``MAIN'' is added to the program unit name 372 of one entry E71, and the same entry "°M°°" is stored in the program type 373 of E71. If the corresponding program unit name is already registered in an entry, a type such as "M" is stored in the program type 373 of the same entry. It is.

After completing the process 130, the program unit analysis unit 2 returns to the process 100 via the process 140, and inputs the next sentence.

After that, in process 100, statement 4 instructing task activation
When 12 is input, it is recognized in step 140 that it is a type of task-related sentence and also a type of CALL-related sentence that instructs task activation, and the following information storage process is performed in step 150.

■ One entry Ell of program unit information 310
O line number 315 is the line number ``302'' of statement 412, type 313 is the type ``task start'' of statement 412, variable name 3
12, variable name "TASK1", program unit name 31.
4, the name of the subroutine activated by the statement 412 “5”
UB2'' are stored respectively.

■ Since this is a statement that instructs to start a task, CALL statement information 3
50, program unit name 351, program unit name “M”
By storing “AIN”, the program unit 410
After securing one CALL statement information for
51 is added, and the type ``task activation'' is added to the type 352 of the CALL statement, and the calling program unit name 35 is added.
The program unit name "5UB2" is stored in 3, and the line number "302" of the statement 412 is stored in line number 354. Please note that the CA in which the corresponding program unit name has already been registered
If LL statement information exists, 1 of the CALL statement information
The CALL statement type 5, calling program unit name 1 line number is registered in the entry.

■ Currently, the program unit name ``5UB2'' is included in any program unit name 372 of the program configuration information 370.
is not registered, so there is only one entry E72.
'5UB2' is added to the program unit name 372, and the reference status 375 (task activation column) of that entry E72 is marked.As a result, the program unit with the program unit name '5UB2' is task activated. Note that the program is called by (.

After completing the process 150, the program unit analysis unit 2 returns to the process 100 and inputs the next sentence.

Thereafter, when the CALL statement 413 is input in process 100, it is recognized in process 140 that it is a type of CALL-related sentence, and the following information storage process is performed in process 150.

■ Add one entry E52 to the CALL statement information 350 that already exists corresponding to the program unit 410, and set the type ``°call'' in the type 352 of the CALL statement and the program unit name in the calling program unit name 353. "5UB3" and the line number "310°" of the sentence 413 are stored in the line number 354, respectively.

■ Currently, the program unit name "'5UB" is included in any program unit name 372 of the program configuration information 370.
3” is not registered, so there is only one entry E.
73 is added and the program unit name 372 is “'5UB3.
", and the reference status 374 of that entry E73 (
CALL statement column). As a result, the program unit with the program unit name “SU B 3” is CA
Record that the program is called by the LL statement.

Below, sentences 414, 415.41 of program unit 410
6 is input, information storage processing similar to that of statement 412 (however,
(excluding storage processing of CALL statement information and storage processing of program configuration information) is performed in process 150, and entry E12. of program unit information 31O shown in FIG. E13. E1
The contents of 4 are registered.

The program unit analysis section 2 starts the first program unit 410.
After completing the processing, the next program unit 420.430
Even if 440 fails, the same processing as in program unit 410 is performed. Therefore, the program unit information 3202 program unit information 330 . Program unit information 340 and CALL statement information 360 are registered in the analysis database 30, and the contents of entry E74 are registered in the program configuration information 370. Note that, at this point, the "configuring program name" column in each entry E71 to E74 of the program configuration information 370 is blank.

When the program unit analysis section 2 determines in step 110 that processing for all program units has been completed, the program unit analysis section 2 ends the program unit analysis processing and passes control to the entire program analysis section 3.

Next, with reference to the flowchart illustrating an example of processing by the entire program analysis unit 3 in FIG. 5, the diagram illustrating an example of event type information in FIG. 6, and the already cited FIGS. The configuration and operation of the analysis section 3 will be explained. The event type information in Figure 6 is stored in the analysis database 3 as shown in Figure 3.
0 shows a part of the event type information generated from the contents of 0, 610 is the event type information of variable name TASKI, 620
is the event type information of the variable name EVENTI.

The entire program analysis unit 3 generates a program configuration group and event type information based on the contents of the analysis database 30, that is, program configuration information, program unit information, and CALL statement information.

Here, the program configuration group is, as mentioned above,
It is a set of program units called from each program unit, starting with the main program unit or the program unit activated by a task.

In this example, there are two program configuration groups: a program configuration group starting with the program unit "MAIN" and a program configuration group starting with the program unit "5UB2". Furthermore, the event type information is information on variables used for task activation, synchronization, and exclusive control, organized by variable name, as described above.

Now, the entire program analysis unit 3 first performs the process 5 in FIG.
At step 10, processing is performed for each group of program configurations. Specifically, first, from the program configuration information 370, the input program unit of the program configuration group (the program unit for which the program scale classification 373 of the program configuration information is set to "M", or the task activation for which the reference status 375 is marked) is (such a program unit) and assigns a program configuration group number to that program. In the case of the program configuration information 370 in FIG. 3, since "M" is registered in the program type 373 of the entry E71, the program unit 410 of "MAIN" is recognized as one of the input robot program units, and the entry E71
The group number "l" is stored in the program configuration number 371. And this MAIN” program unit 41
Whether or not there is a program unit called from 0 is searched in order from the CALL statement information 350 corresponding to the program unit 410. In this case, since "5UB3" is included in the CALL statement information 350, it is stored in the program name 376 column of entry E71. Next, it is checked whether there is a program unit called from this '5UB3', but since there is no CALL statement information corresponding to '5UB3', it is recognized that such a program unit does not exist. , entry E71
Only "5UB3" is stored in the column of program name 376, and the group with number "1" is stored as 'MAIN' and '
5UB3'' are recognized as two program units.

Similarly, in the program configuration information 370, reference status 3
"Task launch" marked with 75 °' 5U
Recognizing that the program unit of B2° is an input robot program unit and that only '5UBI' belongs to the group whose head is "'5UBI", the group number is set in the program configuration number 371 of entry E72 of the program configuration information 370''. 2” and '5U' in the column of the program name 376.
BI” is stored.

After completing the grouping process of the program configuration, the entire program analysis unit 3 performs processes 511 to 519 for each group.
Process.

First, the process SZt extracts the group with group number "1". Note that if it is determined in the next process 512 that the processes of all program configuration groups have been completed,
In step 520, error determination processing is performed. In this case, the group with group number “1” is extracted and processing 5 is performed.
Proceed to step 13, where the relevant program composition group
One program unit name is extracted from the process 514-5.
]9. In this case, in process 513, the program unit name "MAIN" in the entry E71 of the program configuration information 370 is first extracted. In addition, the following process 5
If it is determined that all program unit names of the program configuration group have been extracted in step 14, processing 511 is performed.
The process returns to the program configuration group retrieval process, and the next program configuration group is extracted.

In this case, in process 514, the program unit name "M"
Since AIN'' has been retrieved, in process 515, M
One variable name "TASKI" is extracted from the program configuration information 310 in FIG. If the determination is made, the process returns to the process 513 for extracting the program unit name and processes the next program unit.

In this case, the variable name “TASKI゛” has been extracted, so proceed to process 517 and retrieve the variable name “TASKI”.
It is determined whether event type information corresponding to "I" already exists. In the first case, since it does not exist, in the next process 518, one event type information 610 shown in FIG.
is secured and 'TASKI' is stored in the variable name 611. Then, in process 519, the following process is performed.

■ Since the type 313 of the entry Ell in the program unit information 310 where the variable name “TASKI” exists is “task activation”, the flag 61 corresponding to “task activation” in the event type table 612 in the event type information 610 is
Turn 3 “On”.

■ The event type 614 of one entry Fil in the event type information 610 is "Task startup pa", and the program configuration group number 615 is stored in the program configuration number 371 in the program configuration information 370.
I N'” program configuration number “1 (Nnl)’”
'MAIN' is stored in the program unit name 616, and the line number '302' stored in the entry Ell of the program unit information 310 is stored in the line number 617.

Variable name “T” stored in program unit information 310
When the processing of "ASKI" is completed, the same program unit information 3
The remaining variable name stored in 10 is “LOCKl”
, ``LOCKl°', ``TASKI'' processing 5
Processes 15 to 519 are executed. Then, when the processing of the program unit "'MAIN" is completed, the group number "1"
Remaining program units belonging to “SUB3”
When the processing for the group number "Pa1" is completed, the processing for the next group number "°°2" is performed in the same manner as described above. As a result, all usage conditions related to the variable name "TASKI" by the source program IO are identified, and event type information such as 610 in FIG.
All usage conditions related to "NTI" are identified and event type information such as 620 is generated.

When the entire program analysis unit 3 finishes processing all program configuration groups, it proceeds to step 520 and performs error determination processing.

In the error determination process in this process 520, based on the event type information for each variable name generated as described above, by checking whether the usage status of the variable name matches a predetermined rule. , detects errors related to synchronous exclusive control of tasks that span program units. For example, when analyzing the event type information 620 of the variable name "EVENTI" in FIG. 6, it is found that the variable name "EVENTI" is used at the start of synchronous wait and the end of synchronous wait by the flag 623, and there is a correspondence. To that extent, there are no errors. However, the group numbers 625 of the program configurations in entries F21 and F22 are both 'Nα2'', and regarding the variable name "EVENTI", there is a synchronous wait start process and a synchronous wait end process outside the same program configuration group number. I know it won't. The fact that there is a synchronized wait start and a synchronized wait end in the same program configuration group means that, for example, if the synchronized wait start process is executed first, the process will stop there, so in this case, the synchronized wait start will be an error. It is determined that At this time, the entire program analysis unit 3 stores information "err" to that effect in the error information 628 of the entry F21 in the event type information 620 of the variable name "EVENTI".

When the entire program analysis section 3 finishes analyzing the entire program, it passes control to the information output section 4. The information output section 4, for example, edits the event type information for each variable name in FIG. Analysis information including information on errors detected by the overall analysis section 3 is output as output information 20.

FIG. 7 shows an example of the output information 20. In this example, with reference to the contents of the error information 628 of entry F21 of the event type information 620, regarding the variable name "EVENTI", message 710 indicates that the synchronized wait start and end only exist within the same program configuration group. The output information with is added is output.

Although the embodiments of the present invention have been described above, the present invention is not limited to the above embodiments, and various other additions and changes are possible. For example, it is possible to reduce the functionality to only detect errors that can be detected without grouping the program structure of the source program to be analyzed. In that case, program structure information, CALL statement information Functions such as generation of program configuration groups, etc. can be omitted.

〔Effect of the invention〕

As explained above, in the source program analysis device of the present invention, each program unit constituting a source program is analyzed, and task activation, exclusive section start, exclusive section end, task waiting, etc. that appear in each program unit,
Generates program unit information that collects information about task-related statements such as synchronous wait start and synchronous wait end, and then uses the generated information to determine how each variable appears in the source program. The system generates event type information indicating whether the synchronous exclusive control is being executed, and detects errors related to synchronous exclusive control based on this event type information. It is possible to detect errors such as not using a variable to end or start a synchronous wait in any of the program units that make up the source program, that is, errors related to synchronous exclusive control of tasks spanning between management programs. becomes.

Also, when analyzing individual program units, it is also possible to determine which program unit is responsible for task activation or CALL.
In addition to generating CALL statement information indicating whether
Generate program configuration information that shows what kind of program units the source program to be analyzed is composed of and what kind of reference relationships exist between the program units, and when analyzing the entire program, use the above information to determine the main program unit. Alternatively, it recognizes a program configuration group, which is a set of program units that are task activated or called from each program unit, starting with the program unit activated by a task, and records the usage status of variables for each variable that appears in the source program, including the program configuration group. By generating event type information indicated by , and detecting errors related to synchronous exclusive control, it is possible to detect, for example, that a variable is used at both the start and end of synchronous waiting, and as long as there is a correspondence and no error exists. However, it is possible to detect errors such as when a synchronous wait start process and a synchronous wait end process for a variable exist only in the same program configuration group.

[Brief explanation of drawings]

The first part is a configuration diagram of an embodiment of the present invention, FIG. 2 is a flowchart showing an example of the processing of the program unit analysis section 2, FIG. 3 is a diagram showing an example of the contents of the analysis database 30, and FIG. 5 shows an example of the original program lO, FIG. 5 shows a flowchart showing an example of the processing of the entire program analysis unit 3, FIG. 6 shows an example of event type report, and FIG. 7 shows the output. 2 is a diagram showing an example of information 20. FIG. In the figure, J...Analysis device 2...-Program unit analysis section 3...Whole program analysis section 4...Information output section 10...Original program 20...-Output information 0...Analysis database 10.320,330,340...Program unit information 50.360...CALL statement information 70...Program configuration information 10.420,430,440...Source program 1
Program unit 10.620 that constitutes 0...event type information

Claims (2)

[Claims] (1) A device for analyzing source programs consisting of multiple program units written in a high-level language and created for computer systems with a multitasking function that divides an executable program into different tasks and executes them in parallel. a program unit analysis unit that inputs and analyzes each program unit of the source program and generates program unit information that collects information about task-related statements appearing in the program unit for each program unit; an analysis database that stores information generated by the unit analysis section; and event type information that indicates the usage status of each variable appearing in the source program for each variable that appears in the source program based on the information stored in the analysis database; The program is characterized by comprising an entire program analysis section that detects errors related to synchronous exclusive control based on event type information, and an information output section that outputs analysis information including information on errors detected by the entire program analysis section. Source program analysis device. (2) An analysis device for a source program consisting of multiple program units written in a high-level language and created for a computer system with a multitasking function that divides an executable program into different tasks and executes them in parallel. In this step, each program unit of the source program is input and analyzed, and program unit information that collects information about task-related statements that appear in the program unit for each program unit and CALL that collects information about CALL-related statements.
a program unit analysis unit that generates statement information and program configuration information of the source program; an analysis database that stores information generated by the program unit analysis unit; and an analysis database that stores information generated by the program unit analysis unit; Recognizes the program configuration group based on the program configuration group, generates event type information indicating the usage status of the variable including the program configuration group for each variable appearing in the source program, and performs synchronous exclusive control based on the generated event type information. A source program analysis device comprising: an entire program analysis section that detects errors related to the program; and an information output section that outputs analysis information including information on errors detected by the entire program analysis section.