JPH08147196A - System call emulator - Google Patents

Abstract

PURPOSE: To provide the system call emulator with which the speedy development and various tests of an application software are enabled by simplifying the descriptions of a table for designating the contents and report timing (internal time) of the immediate report, complete report and asynchronous report of a system call by using a default table and a designation table while combining them. CONSTITUTION: The information required for report processing is decided based on the issued part of the program of the system call out of the information described in two kinds of tables of a default table 20 for describing the contents in the case of normally completing the system call and a designation table 19 for describing only the part, where the system call appears, in the application program and the contents of the immediate report, complete report and asynchronous report corresponding to that system call, or the like, and the required table is selected by a table selecting part 17.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a system call emulator which emulates a system call for an application in order to develop and test the application independently of hardware.

[0002]

2. Description of the Related Art Conventionally, in order to develop application software independently of hardware development without using actual hardware, a prescribed system call is issued as shown in FIG. Always used a stub table that returns a normal system call return. In this conventional method, a normal return is described for each system call type in the stub table, and a report corresponding to the system call type is returned each time each system call is called.

As another method, as shown in FIG. 7B, in the designated table, for all system calls appearing in the application, all report contents corresponding to each system call are described. In addition, each time a system call is called, the corresponding report content is returned.

[0004]

In the above-mentioned conventional technique, when the stub table is used, it can be used only for verifying whether or not the description of the system call name or the system call parameter related to the system call is correct. In the case of the method of describing the system call issued by, it required a lot of effort to create the designated table for describing the report contents. Furthermore, when the stub table is used, the application software cannot be verified when the system call does not return a normal system call return.

The present invention has been made in view of the above,
The purpose of this is to use the default table and the specified table in combination to facilitate the description of the table for specifying the contents of system call immediate report, completion report, asynchronous report and notification timing (internal time). , Early development of application software,
It is to provide a system call emulator that enables various tests.

[0006]

In order to achieve the above object, the system call emulator of the present invention is a system call emulator that simulates a system call used by an application. Immediate report description part that describes the contents of immediate report of system call, completion report description part that describes the contents and timing (internal time) of completion report of system call, content and timing of asynchronous report of system call (internal time) An asynchronous report description part,
A default table that has a cycle report description part that describes the contents and timing (internal time) of the system call cycle report, and an optional information description part that describes other information, and the above-mentioned default table as information corresponding to the system call. In order to uniquely identify the system call in the program, in addition to the immediate report description section, the completion report description section, the asynchronous report description section, the periodic report description section, and the option information description section, which are the descriptions of the system call correspondence information. Necessary information for the file name of the program described by the system call, the line in which the system call is described in the file, and the number of times the system call is issued when the system call is repeatedly executed in the program. Match the position description part with the number of times to describe A table selection unit that has a function of selecting a required table from the specified tables and the information described in both tables, which is necessary for report processing, is determined based on the issue point in the system call program. The point is to have and.

Further, the system call emulator of the present invention is provided with a log table generating section for generating the log table for recording the system call issuance history of the program with the same configuration and content as the designated table. The point is to use the log table as the designated table.

[0008]

In the system call emulator of the present invention, a table for specifying the contents of the immediate report, the completion report, the asynchronous report and the notification timing (internal time) is provided as a default describing the contents when the system call is completed normally. Immediate report, completion report, asynchronous report corresponding to the occurrence of the system call in the application program and the system call to return the immediate report, the completion report, and the asynchronous report at the specified timing (internal time) and contents Divide into a specified table that describes only the contents of
By providing a table selection unit that automatically selects these tables, the contents of the system call and the return timing (internal time) can be freely controlled and the table description amount can be reduced.

Further, in the system call emulator of the present invention, by providing the log table generating section for generating the log table having the same format as the designated table, the description of the table for the abnormality processing becomes easy.

[0010]

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of a system call emulator according to an embodiment of the present invention. In the figure, the emulator 12 is composed of a system call issuance processing unit 13, a periodic processing unit 14, a system call program position management unit 15, a processing queue 16, a table selection unit 17, and a log table generation unit 18.

The system call issue processing unit 13 is
This is a part that is executed when a system call is issued from the application program 11. Cycle processing unit 1
Reference numeral 4 is a part that is periodically executed by the emulator at regular time intervals. The system call program position management unit 15 indicates at which line in the program file the issued system call is described, and a part that associates with what number of times the program is being executed during execution of the program. Is. The processing queue 16 is for waiting for a report to be processed by the periodic processing. The table selection unit 17 determines whether the information about the issued system call is described in the default table 20 or the designated table 19.
The log table generation unit 18 records the execution content of the process as the log table 21 in the same format as the designation table 19.

Next, with reference to the flow chart shown in FIG. 2, the processing at the time of issuing a system call will be described.

The system call issue processing unit 13 is
When the system call is started when the system call is issued, first the system call program file position management unit 15 is inquired about the line and the number of times of the system call in the file, and these are acquired (step S11). Whether the system call is described in the default table 20 Designation table 1
9 is inquired to the table selection unit 17, the table is selected (step S12), and the description content is read from the selected table (step S1).
3). Then, a report message is created based on the read description contents and put in the processing queue (step S1).
4). The immediate report is returned to the application 11 (step S15).

Next, the periodic processing will be described with reference to the flowchart shown in FIG.

When the periodic processing unit 14 is periodically activated, it checks whether or not there are any unconfirmed report messages in the processing queue (step S21). However, if there is, the remaining processing waiting time of the message is subtracted (step S22), and it is checked whether or not there is a remaining remaining time of the message in the processing waiting queue of 0 or less. The message which has reached the processing waiting time inside is searched for (step S23). If there is no remaining time of 0 or less, the process returns to step S21 and the same process is repeated, but if there is, the report message is returned to the application (step S24) and the process of the log table 21 is performed (step S24). S25), and returns to step S21. The process of step S25 is performed when the log table generation is designated.

The above-described periodic processing is executed, for example, every one second cycle, and when the cycle processing unit 14 is activated, all messages that meet the conditions are processed.

FIG. 4 is a diagram showing a general configuration of the default table and the designated table. In the figure, 20
Reference numeral 1 indicates the configuration of the default table, and 202 indicates the configuration of the designated table. Default table 201
Is composed of a system call name description part, an immediate report description part, a completion report description part, an asynchronous report description part, a periodic report description part, and an option information description part. The designation table 202 is composed of a system call name description part, a position description part, an immediate report description part, a completion report description part, an asynchronous report description part, a periodic report description part, and an option information description part.
In FIG. 4, each description part is separated by ";", and the end of the scenario is displayed by ";;".

FIG. 5 shows a configuration and a specific example of each description part of the position, immediate report, completion report, asynchronous report, and periodic report. Here, the option information description part is determined as necessary, and the structure is undefined, so the description thereof is omitted.

The position description part is an alphanumeric string representing the name of the file in which the system call is described, a numeric string representing in which line of the file the system call is described,
When a system call is executed several times during program execution, it is composed of a string of numbers that indicates the line of execution at which the specified value is returned. For example, "FILE003,1
0, 1 ". As described above, the system call is uniquely specified in the program by the three elements.

The immediate report description section, the completion report description section, the asynchronous report description section, and the periodic report description section have the same structure in the default table and the designated table.

The immediate report description section is an alphanumeric string expressing the immediate report contents specified for each system call.
For example, "00 00 00 00".

The completion report description section represents an alphabetic character string "FIN" for indicating that this description is a completion report, a numerical string representing a waiting time from issuing a system call to returning a completion report, and content of the completion report. It is composed of an alphanumeric string. For example, "FIN, 5,0000 00 00".

The asynchronous report description part is an alphabetic character string "ASY" indicating that this description is an asynchronous report, a numerical string representing the waiting time from the issuance of a system call to the return of the asynchronous report, and an alphanumeric character representing the contents of the asynchronous report. Composed of columns.
For example, "ASY, 10, 00, 00, 00, 08".

The periodic report description part is an alphabetic character string "CYC" indicating that this description is a periodic report, a numeric string representing the waiting time from the issuance of a system call to the return of the periodic report, and an alphanumeric character representing the periodic report contents. Composed of columns. For example, "CYC, 30,00 0000 00-00 0
0 00 01-00 00 00 02 02 ", where" 00 00 00 00 00 "and" 00 0
0 00 01 "and" 00 00 00 00 02 "are used as report contents for the first time, second time, and third time, respectively." 00 00 00 00 00 "is used as report content for the fourth time. 00 00 0
This information is repeatedly used in the order of 1 "," 00 00 00 02 ".

FIG. 6 is a diagram showing an example of an application program and a table. FIG. 6A shows a program example, and FIG. 6B shows a table example.

In FIG. 6, the application program uses the system call Allocate-Resource.
e 0; is issued twice, but FIL is specified in the specified table.
As an immediate report of the system call on the 8th line of E001 "
Since "00 00 00 10" is specified to be returned, "00 00 00 00" is returned as a report at the time of the first issue, and the specified value "00 0000 10" is returned at the time of the second issue. "Is returned.

[0028]

As described above, according to the present invention,
In the system call emulator, the timing (internal time) and contents of various system call reports can be divided into normal cases and special cases, so that it is not necessary to describe the operation table of the system call emulator for each system call. There is an advantage that the description amount of the operation table is reduced and the operation of table creation is reduced. Even when the system call does not return a normal report, the application software can be verified by using the designated table.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of a system call emulator according to an exemplary embodiment of the present invention.

FIG. 2 is a flowchart showing processing when a system call is issued.

FIG. 3 is a flowchart showing a periodic process.

FIG. 4 is a diagram for explaining a general configuration of a table.

FIG. 5 is a diagram illustrating a configuration and a specific example of each description unit of a table.

FIG. 6 is a diagram for explaining the relationship between the contents of an application program file and a table.

FIG. 7 is a diagram showing a conventional example.

[Explanation of symbols]

 11 application program 12 emulator 13 system call issue processing unit 14 cycle processing unit 15 system call program position management unit 16 processing queue 17 table selection unit 18 log table generation unit 19 designated table 20 default table 21 log table

Claims (2)

[Claims] 1. In a system call emulator that simulates a system call used by an application, a system call name description section that describes a system call name,
An immediate report description part that describes the contents of the system call immediate report, a completion report description part that describes the contents and timing of the system call completion report, an asynchronous report description part that describes the contents and timing of the system call asynchronous report, A default table having a cycle report description section that describes the contents and timing of the system call cycle report, and an optional information description section that describes other information, and system call correspondence information in the default table as information corresponding to the system call. The immediate report description part, the completion report description part, the asynchronous report description part, which are the description parts of
In addition to the periodic report description part and option information description part, the file name of the program described by the system call and the system call described in the file are the information necessary to uniquely identify the system call in the program. And a specified table that also has a position description section that has the number of times that the system call is issued when the system call is repeatedly executed in the program; The system call, which includes a table selection unit that is a function that determines the information necessary for the report processing from among the stored information based on the issue location in the program of the system call and selects the necessary table. emulator. 2. A log table generation unit for generating a log table for recording a system call issuance history of a program with the same configuration and contents as the designated table, and using the generated log table as the designated table. The system call emulator according to claim 1.