JPH05224908A - Program production system - Google Patents

Abstract

PURPOSE:To obtain debug information even if it is not under the environment of a debugger without using an interrupting instruction by providing an adding means for deciding whether addition of a debug routine is necessary or not, and generating and embedding the debug routine. CONSTITUTION:In the case where addition of a debug routine is acknowledged in a translating means 22, a debug routine addition deciding means 23 is actuated, and by judging what kind of debug routine is the most suitable, a debug routine generating means 24 is actuated. The debug routine generating means 24 generates the debug routine being the most suitable for its source program 1, based on the kind of the debug routine decided by the debug routine addition deciding means 23 and a debug routine data base 25. A debug routine embedding means 26 executes a processing for embedding the debug routine generated by this debug routine generating means 24 into an object module 3 which is being generated at present by the translating means 22.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a program production system for creating computer software.

[0002]

2. Description of the Related Art FIG. 4 is a conceptual diagram showing a conventional program production system, and FIG. 5 is a block diagram showing its debugging method. In FIG. 4, 1 is a source program written in a high-level language and is a target of compilation, and 2
Is a compiler for compiling the source program 1. 3 is the source program 1 with this compiler 2
The object modules are respectively generated, and 21 is a grammar analyzing unit and 22 is a translating unit.
Reference numeral 4 is a linker that links the generated object module 3, and reference numeral 5 is a load module (object program) generated by the linker 4.

Further, in FIG. 5, 5 is the load module (object program), 6 is map information storage means for extracting address information of the load module 5, and 6
Reference numeral 1 is map information of the load module 5 obtained by the map information storage means 6. Reference numeral 7 is a loading memory as a storage means for loading the load module 5, and 8 is a load module 5 on the loading memory 7.
It is an interrupt instruction setting means that applies a patch to. Reference numeral 9 is a real pattern save area for saving the original instruction when a patch is applied, and 10 is a dynamic debugger for performing debug processing.

Next, the operation will be described. Compiler 2
Uses the built-in grammar analysis means 21 and translation means 22 to perform grammar analysis and code conversion processing of the read source program 1 to generate the object module 3. Similarly, the object module 3 is generated for each of the other source programs 1. The object module 3 thus generated is sent to the linker 4 and linked, and the load module (object program) 5 is generated.

Next, debugging of the load module (object program) 5 thus generated will be described. At the time of debugging, the address to be debugged by the load module 5 is obtained based on the map information 61 generated by the map information storage means 6, and the instruction at the address on the loading memory 7 is replaced by the interrupt instruction setting means 8. As a result, the debug routine of the dynamic debugger 10 is called and the load module 5 is debugged.

As a document describing a technique related to debugging a program produced by such a conventional program production system, there is, for example, Japanese Patent Laid-Open No. 63-21.
7431 and the like.

[0007]

Since the conventional program production system is constructed as described above, the address of the program is obtained and the instruction is replaced with the interrupt instruction, and the debug routine of the dynamic debugger 10 is started. Since debugging is performed, it is necessary to prepare an interrupt vector for an interrupt that calls the dynamic debugger 10, which is irrelevant to the actual program, and the passing of arguments to the function, etc., must be done in the source file list (or program list, etc.). ), It is necessary to intervene in the debugging, and the burden on the user is large.
The program can be debugged only in the environment where the debugger operates (under the environment of the debugger), and there is a problem that the environment at the time of actually executing the program and the environment at the time of debugging may be different.

The present invention has been made in order to solve the above problems, and does not use interrupt instructions when performing debugging, and debug information can be obtained even when the environment of the debugger is not used, and the user The purpose is to obtain a small program production system.

[0009]

In the program production system according to the present invention, a debug routine addition judging means for judging the necessity of adding a debug routine to a source program, and as a result of the judgment, it is judged that addition should be made. In this case, a debug routine adding means including a debug routine generating means for generating a debug routine most suitable for the source program and a debug routine embedding means for embedding the generated debug routine is provided.

[0010]

According to the debug routine adding means of the present invention, the debug routine addition judging means judges whether or not the debug routine needs to be added to the source program, and when it is judged that the debug routine should be added, as a result of the judgment. Uses the debug routine generating means to generate the most suitable debug routine for the source program, and embeds the generated debug routine in the program by the debug routine embedding means so that interrupt instructions are not used when performing debugging. , It is possible to realize a program production system which can obtain debug information even if it is not under the environment of a debugger and place a small burden on the user.

[0011]

【Example】

Example 1. An embodiment of the present invention will be described below with reference to the drawings. In FIG. 1, 1 is a source program, 2 is a compiler, 3 is an object module, 4 is a linker, 5
Is a load module (object program), 21 is a grammar analysis means, and 22 is a translation means, which are the same as or equivalent to those of the conventional ones given the same reference numerals in FIG.

Reference numeral 20 is a debug routine adding means provided in the compiler 2. 23 is the source program 1
Is a debug routine addition judging means for judging whether or not a debug routine should be added, and 24 is most suitable for the source program 1 when it is judged by the debug routine addition judging means 23 that it should be added. It is a debug routine generating means for generating a debug routine. Reference numeral 25 is a debug routine database that manages debug routines applicable to all programs. Reference numeral 26 is an object generated by the translation means 22 by translating the debug routine generated by the debug routine generating means 24 and the debug routine database 25. It is a means for embedding a debug routine in the module 3. The debug routine adding means 20 includes the debug routine addition determining means 23, the debug routine generating means 24, and the debug routine database 2.
5 and the debug base embedding means 26.

Next, the operation will be described. Compiler 2
Is similar to the conventional case, the grammar analysis means 21 and the translation means 2
2 is used to perform grammar analysis and code conversion processing of the read source program 1. At that time, the translation means 2
If the addition of the debug routine is permitted in 2, the debug routine addition determining means 23 is activated. When the debug routine addition determining means 23 is activated, it determines which debug routine is most suitable and activates the debug routine generating means 24.

The debug routine generating means 2 which has been activated
4 is the type of the debug routine judged by the debug routine addition judging means 23 (for example, for a function,
A debug routine most suitable for the source program 1 is generated based on the access to resources such as a disk) and the debug routine database 25. Debug routine embedding means 2
6 executes processing for embedding the debug routine generated by the debug routine generating means 24 in the object module 3 currently being generated by the translating means 22.

The compiling process by the compiler 2 is completed by repeating the processes by the grammar analyzing means 21, the translating means 22 and the debug routine adding means 20. The object module 3 generated at this time has only the debug routine added,
Structurally and in terms of code, there is no difference from that generated by the conventional compiler 2. The object module 3 thus generated is loaded by the linker 4 into the load module (object program) 5 as in the conventional case.
Linked to.

FIG. 2 is an explanatory diagram showing the flow of processing when the generated load module 5 is debugged. In the figure, 11a to 11d are program bodies obtained by compiling the source program 1, and 12a to 12d.
Reference numeral c is a debug routine generated and added based on the source program 1. The process is executed sequentially from the upper part to the lower part of the figure, but the apparent process proceeds as shown by the broken line arrow 13 and the user who executed this program should not be aware of the execution of the debug routines 12a to 12c. Is shown. This debug routine 12a-12c
Debug information 14a to 14c obtained by executing
Are stored in a debug information storage area 15 of a file or a memory area and provided to a user or a debugger.

Embodiment 2. In the first embodiment described above, the case where the debug routine adding means 20 is arranged next to the translating means 22 has been described.
0 may be placed at any stage of the compilation process in the compiler 2.

Example 3. In the first embodiment, the debug routine is embedded in the object module 3 whose code has been converted to the machine language level. However, the debug routine generated at the source level is added to the source program 1 to generate an intermediate source program. However, it may be supplied to the grammar analysis means 21. FIG. 3 is a conceptual diagram showing such an embodiment, and the portions corresponding to those of FIG. 1 are designated by the same reference numerals and the description thereof will be omitted. In the figure, 27 is a debug routine adding means 20.
The intermediate source program is generated by the above and is supplied to the grammar analyzing means 21.

Next, the operation will be described. The debug routine addition determining means 23 determines whether or not a debug routine needs to be added based on the read source program 1.
When it is determined that the addition is necessary, the debug routine generating means 24 is activated to generate an optimum debug routine, and the debug routine embedding means 26 is caused to embed the debug routine in the source program 1 to generate the intermediate source program 27. To do. On the other hand, when it is determined that there is no need to add the source program 1, the source program 1 is directly written as the intermediate source program 27 without being changed. The intermediate source program 27 generated in this way is sent to the grammar analysis unit 21 for grammar analysis, and the translation unit 22 further performs code conversion processing to generate the object module 3.

Further, in the third embodiment, the form of the debug routine generated by the debug routine generating means 24 is explained as being the same as that of the source program 1, but it is generated in the intermediate code form which is a unique code form. You may.

Further, in each of the above-described embodiments, the case where the debug routine automatically generated based on the source program 1 is added has been described. However, a debug routine selected from those prepared in advance may be added. The same effect as that of the above embodiment is obtained.

Further, in each of the above embodiments, the case where the generation / addition of the debug routine is performed at the stage of the compile process is shown, but it may be performed at another stage such as linking. When the debug routine is generated and added at the time of compiling, the source program 1 can be referred to, so that the debug routine suitable for the program can be added. Therefore, even when the arguments are passed to the function at the time of debugging, the user does not need to make a judgment and the burden on the user is reduced.

Further, although the case where the source program is translated to the machine language level has been described, it may be applied to a translator that generates up to the intermediate code level, and the same effect as that of the above embodiment is obtained.

In the above embodiment, the debug routine database 25 is used as the resource for generating the debug routine, but the debug routine generating means itself may generate the debug routine.

[0025]

As described above, according to the present invention, since the debug routine adding means adds the debug routine to the program body, it is not necessary to generate an interrupt, and an unnecessary interrupt in an actual program. Not only does it not have to be used, but it is also possible to obtain debug information without a debugger, and debug can be performed outside the environment of the debugger. By using this debug information, the program can be actually executed. Even without doing so, it is possible to debug and analyze the program.

[Brief description of drawings]

FIG. 1 is a conceptual diagram showing a first embodiment of the present invention.

FIG. 2 is an explanatory diagram showing a flow of processing at the time of debugging a program generated in the above embodiment.

FIG. 3 is a conceptual diagram showing a second embodiment of the present invention.

FIG. 4 is a conceptual diagram showing a conventional program production system.

FIG. 5 is a block diagram showing the debugging method.

[Explanation of symbols]

 1 Source Program 20 Debug Routine Adding Means 23 Debug Routine Addition Determining Means 24 Debug Routine Generating Means 26 Debug Routine Embedding Means

Claims (1)

[Claims] 1. A debug routine addition judgment for judging whether or not a debug routine should be added to the source program in a program production system for generating a program by analyzing the grammar of the source program and converting the code thereof. Means, a debug routine generation means for generating a debug routine most suitable for the source program when the debug routine addition determination means determines that the debug routine should be added, and a debug generated by the debug routine generation means. A program production system comprising a debug routine adding means including a debug routine embedding means for performing routine embedding processing.