Priority information display system

[0002] This invention relates to a priority information display system that displays information on the priorities of processes effective in debugging, for example, a concurrent program.

[0003] In a concurrent-program execution environment, priority is generally set for units of concurrent operations, called tasks, processes, or objects, (hereinafter, referred to as “processes”). Priority is set for each process. Each process operates concurrently with other processes according to the scheduling from the operating system. As a general rule, in a specific operating system where priority is changed dynamically, the higher the priority of a process, the sooner the process will be executed.

[0004] In recent years, an operating system with a priority inheritance algorithm that causes a process to inherit the priority of another process has been provided. In priority inheritance by the algorithm, the present priority of the process that is to inherit priority is changed dynamically to the priority of the process from which the priority is inherited.

[0005] Explanation will be given, provided that a single process has a “initial basic priority”, a “basic priority”, and a “present priority”. The “initial basis priority” means the value of priority given to a process in the initial stage and remains unchanged, as a general rule. The “basic priority” means the value of priority that changes only due to a specific factor (a specific system call) excluding the priority inheritance, as a general rule. The “present priority” means the value of priority that the operating system uses in scheduling, as a general a rule. The value of the present priority changes, depending on various factors including priority inheritance.

[0006] Some dynamic changes of priority are related to inheritance and other dynamic changes of priority are not related to inheritance. In the former case, that is, when dynamic changes of priority are related to inheritance, the factors triggering the change of priority include, for example, the issue of an interprocess synchronizing system call and the occurrence of an event, such as message exchange.

[0007] In the latter case, the change of the basic priority is taken as example.

[0008] A single process has “process states”.

[0009] The “process states” mean the states of a process scheduled by the scheduler in the operating system.

[0010] Here, they indicate three states distinguished from each other by “Ready,” “Wait,” and “Run.”

[0011] In the environment for debugging concurrent programs executed on the operating system using the priority inheritance algorithm, the desired program is debugged by recording the history of events occurred during the execution of the program and observing the behavior of the process.

[0012] The known methods of displaying information on priority, such as the current priority or the basic priority, include a method of recording the value of priority after the change at the time of issuing a priority change system call and a method of checking the priorities in unison with a specific timing. With these methods, however, the obtained priorities are only displayed in numerical values, which makes it impossible to display information on priority inheritance effectively.

[0013] It is, accordingly, an object of the present invention to overcome the disadvantage in the prior art by providing the following priority information display systems:

[0014] (1) A priority information display system that displays information on priority effective in debugging concurrent programs or the like.

[0015] (2) A priority information display system that displays the priority information three-dimensionally so as to provide the user with the priority information effectively.

[0016] The foregoing objects are accomplished by providing a priority information display system which operates with an operating system that controls an execution of a plurality of processes having their respective priorities and enables an inheritance of priority between said processes, said priority information display system comprising:

[0017] acquisition means for acquiring from said operating system a priority information including information on the inheritance of the priorities between said processes; and

[0018] display means for displaying said priority information acquired by said acquisition means.

[0019] According to the present invention, when a specific event related to the priorities of processes has taken place, not only specific process information on the event can be acquired and displayed, but also the behavior of processes, the change of priority, the cause of priority change, etc. can be recorded and displayed to the user, so that the user can easily find bugs or the like in the application program stemming from priority inheritance caused by an unexpected behavior of the process. Therefore, it is possible to provide a priority information display system that displays the program information effective in debugging the concurrent program.

[0020] Additional objects and advantages of the present invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the present invention.

[0021] The objects and advantages of the present invention may be realized and obtained by means of the instrumentalities and combinations particularly pointed out in the appended claims.

[0022] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate presently preferred embodiments of the present invention and, together with the general description given above and the detailed description of the preferred embodiments given below, serve to explain the principles of the present invention in which:

[0023] FIG. 1 is a block diagram of the configuration of a priority display system according to the present invention;

[0024] FIG. 2 is a flowchart to help explain the flow of the recording process in the priority information acquisition section 3;

[0025] FIG. 3 illustrates an example of the screen that specifies a process to be recorded and the priority of the process;

[0026] FIG. 4 shows an example of the pieces of priority information recorded;

[0027] FIG. 5 is a flowchart to help explain the flow of processing at the time when priority inheritance has occurred;

[0028] FIG. 6 shows an example of the pieces of priority information (inheritance) recorded by the priority information recording section 4;

[0029] FIG. 7 is a flowchart to help explain the flow of the canceling process of priority inheritance;

[0030] FIG. 8 shows an example of the pieces of priority information (inheritance cancellation) recorded by the priority information recording section 4;

[0031] FIG. 9 is a flowchart of the basic priority changing process;

[0032] FIG. 10 shows an example of the pieces of priority information (basic priority change) recorded by the priority information recording section 4;

[0033] FIG. 11 is a flowchart of the process at the time when the process state has changed;

[0034] FIG. 12 shows an example of the pieces of priority information (process state) recorded by the priority information recording section 4;

[0035] FIG. 13 illustrates an example of a list display of pieces of priority information;

[0036] FIG. 14 is a flowchart of the three-dimensional display process of priority information;

[0037] FIG. 15 illustrates an example of a three-dimensional display of priority information; and

[0038] FIG. 16 illustrates another example of a three-dimensional display of priority information.

[0039] Hereinafter, referring to the accompanying drawings, embodiments of a priority information display system according to the present invention will be explained. In a first embodiment, a system that acquires information on the priorities of processes, including priority inheritance, from the operating system and displays a list of pieces of the priority information will be explained. In a second embodiment, a system that displays the priority information three-dimensionally.

[0040] (First Embodiment)

[0041] FIG. 1 is a block diagram of the configuration of a priority information display system according to the present invention. The priority information display system of the present invention comprises a process specifying section 2, a priority information acquisition section 3, a priority information recording section 4, and a display section 5, all of which are under the control of an operating system 1.

[0042] The operating system 1 used in the present invention controls the execution of a plurality of processes constituting an application program (a concurrent program) and intermediates between these processes and the input and output devices. One known operating system of this type is UNIX. Each process operates in a unique virtual address space in the computer system. Control of the execution of processes by the operating system means controlling the state of the processes, giving a suitable priority to each process, and thereby managing the order in which the processes will be executed.

[0043] The operating system 1 has a function related to the above-described priority inheritance algorithm. Namely, the operating system 1 enables the inheritance or cancellation of priority between a plurality of processes. There may be a case where the function is provided as an additional function of the operating system 1.

[0044] The process specifying section 2 is used for the user to specify a specific process, while seeing the display section 5, as described later.

[0045] The priority information acquisition section 3 holds the identifier for a process to be recorded that has been specified by the user and acquires from the operating system 1 information on the priority of the process, priority inheritance, and the change of the process state. According to the identifier for a process to be recorded, the section judges whether or not the acquired information is about the process to be recorded. If the information is about the process to be recorded, the section will send the acquired information to the priority information recording section 4.

[0046] Information (priority inheritance information) on a process related to priority inheritance includes the information used to let the user know that priority is inherited from a first process to a second process and that the priority given to the first process is canceled.

[0047] The priority information recording section 4 holds the specific pieces of information acquired by the priority information acquisition section 3. For example, it may be a file in a UNIX system or it may be held in the memory space.

[0048] The display section 5 displays the priority information etc. to the user on the basis of the specific information stored in the priority information recording section 4. The display section 5 also acts as the user interface for the user to specify a process.

[0049] Now, the operation of the priority information display system of the embodiment will be explained.

[0050] It is assumed that the application program (concurrent program) is made up of, for example, three processes, process A, process B, and process C, which operate cooperatively using a priority inheritance semaphore (not shown). Here, explanation will be given as to how process B inherits the priority of process A and operates.

[0051] FIG. 2 is a flowchart to help explain the flow of the recording process at the priority information acquisition section 3.

[0052] First, the user starts up the priority information acquisition section 3 to prepare to start the application program including the process to be recorded (ST 21).

[0053] It is assumed in the embodiment that process A, process B, and process C have been specified for processes to be recorded (ST22) and have been given priority levels 3, 4, and 5, respectively. FIG. 3 illustrate an example of the screen used to specify the processes to be recorded and the priorities of the processes. The figure shows that the user has finished setting process A and selected the icon corresponding to process B as a process to be recorded, thereby entering the initial priority. The name of the selected process to be recorded and the priority of the process are sent to the priority information acquisition section 3, which holds it.

[0054] The priority information acquisition section 3 acquires information on the priority of the process to be recorded and information on the state of the process (hereinafter, referred to as the “priority information”) under the control of the operating system 1 and starts to record (ST23, ST24). The operating system 1 controls the execution of processes, while supervising the priorities of processes and their states, so it is possible to acquire the pieces of information by issuing a system call or the like to the operating system.

[0055] The priority information acquisition section 3 acquires the priorities of processes and their process states from the operating system 1 and records the priority information (ST25).

[0056] FIG. 4 shows an example of the pieces of priority information recorded. As shown in the figure, the priority information acquisition section 3 records pieces of priority information in the following fields: “PROCESS IDENTIFIER,” “TYPE,” “DESCRIPTION,” and “CAUSE.”

[0057] Then, the user starts up the application program including the processes to be recorded (ST26).

[0058] During the execution of the application program, the priority information on the processes to be recorded are recorded according to the occurrence of a specific event (ST27). After the application program has come to an end (ST28), the recording of the priority information is completed (ST29) and a list of the pieces of priority information recorded up to this point is displayed (ST30). The recorded priority information can be read and displayed whenever necessary at the request of the user.

[0059] In the embodiment, the priority information acquisition section 3 is started by the notice from a priority inheritance/priority change/process state change sensing program previously built in the operating system 1. The sensing program is provided as event sensing means for sensing specific events concerning the priorities of processes, including priority inheritance, priority cancellation, basic priority change, and an event related to process state change.

[0060] Next, explanation will be given about the flow of processing in a case where priority inheritance has occurred in the course of executing the application program.

[0061] FIG. 5 is a flowchart to help explain the flow of processing at the time when priority inheritance has occurred.

[0062] When the inheritance of priority has taken place during the execution of the application program (ST51), the priority information acquisition section 3 judges whether or not the process that has inherited the priority is a process to be recorded (ST52). When having judged that the process that has inherited the priority is a process to be recorded, the priority information acquisition section 3 asks the operating system 1 about the inheritance priority and the identifier for the process (source process) from which the priority is inherited and acquires those pieces of information (ST53). Then, the priority information acquisition section 3 sends the inheritance priority information together with the process identifier and type of the process to be recorded to the priority information recording section 4 as inheritance priority information (ST54). The priority information recording section records the inheritance priority information (ST55).

[0063] FIG. 6 illustrates an example of the pieces of inheritance priority information recorded by the priority information recording section 4. The example of the figure shows that priority inheritance has occurred for process B (destination process) whose inheritance priority is 3 and the process that has inherited the priority is process A (source process).

[0064] Next, explanation will be given about the flow of processing in a case where the cancellation of priority inheritance has occurred during the execution of the application program.

[0065] FIG. 7 is a flowchart to help explain the flow of canceling the priority inheritance.

[0066] When the cancellation of the priority inheritance has taken place during the execution of the application program (ST71), the priority information acquisition section 3 judges whether or not the process for which the cancellation has occurred is a process to be recorded (ST72). When having judged that the process for which the cancellation has occurred is a process to be recorded, the priority information acquisition section 3 acquires the process identifier and type (inheritance cancellation) of the process and information on the cause of the cancellation and sends these pieces of information to the priority information recording section 4 (ST73). The priority information recording section 4 records them (ST74).

[0067] FIG. 8 shows an example of pieces of information on the cancellation of the priority inheritance recorded by the priority information recording section 4. The example of the figure shows that the cancellation of the priority inheritance has occurred for process B and the cause of the cancellation has come from semaphore A.

[0068] Next, explanation will be given about a case where the change of the basic priority has taken place during the execution of the application program.

[0069] FIG. 9 is a flowchart for the process of changing the basic priority.

[0070] When the change of the basic priority has occurred during the execution of the application program (ST91), the priority information acquisition section 3 judges whether or not the process for which the change of the basic priority has occurred is a process to be recorded (ST92). When having judged that the process for which the change has occurred is a process to be recorded, the priority information acquisition section 3 acquires from the operating system the basic priority after the change and the identifier for the source process who has changed the basic priority (ST93) and sends these together with the process identifier and the type of information (i.e., basic priority change) to the priority information recording section 4 (ST94). The priority information recording section 4 records the sent information as information on the basic priority change (ST95).

[0071] FIG. 10 illustrates an example of the pieces of information on the basic priority change recorded by the priority information recording section 4. The example of the figure shows that the change of priority has taken place for process B and the priority of process B has been changed to basic priority 6 specified by process C.

[0072] Next, explanation will be given about a case where the change of the process state has occurred during the execution of the application program.

[0073] FIG. 11 is a flowchart to help explain the flow of processing in a case where the change of the process state has taken place.

[0074] When the change of the process state has occurred during the execution of the application program (ST111), the priority information acquisition section 3 judges whether or not the process for which the change of the process state has occurred is a process to be recorded (ST112). When having judged that the process for which the change of the process state has occurred is a process to be recorded, the priority information acquisition section 3 acquires the process state after the change from the operating system (ST113) and sends it together with the process identifier and the type of information (process state change) to the priority information recording section 4 (ST114). The priority information recording section 4 records these pieces of information as information on the process state (ST115).

[0075] FIG. 12 illustrates an example of pieces of information on the process state recorded by the priority recording section 3. The figure shows that the change of the process state has taken place for process B and that the state of process B after the change is “Ready,” and the cause of the change has come from Scheduler.

[0076] As described above, when the occurrence of priority inheritance, the cancellation of priority inheritance, the change of the basic priority, or the change of the process state has been occurred, the priority information recording section 4 manages these events by unique numbers. Then, the information necessary for displaying the priority information is read out at the request of the priority information display section 3.

[0077] FIG. 13 shows a list of pieces of priority information classified by process information No.

[0078] In the figure, process No. 1 to No. 6 are pieces of process initial information. The figure shows that immediately before No. 7, the application program has been started and process B has been executed as a result of the scheduling of the operating system 1. Thereafter, although not shown in the process information, process B is assumed to have acquired semaphore A.

[0079] Process information No. 8 shows that process B has issued a system call that changes the process state of process A and has brought process A into “Ready” state. As a result, the operating system 1 performs scheduling.

[0080] Process information No. 9 and No. 10 show that as a result of scheduling, process A has been selected, process B has gone into “Ready” state, and process A has gone into “Run” state.

[0081] Process information No. 11 shows that process C has issued a system call that changes the basic priority of process B and the priority of process B has taken the value of 6.

[0082] Process information No. 12 shows that process A has failed to acquire semaphore A that process B has and has gone into “Wait” state.

[0083] Process information No. 13 shows that process B has inherited priority 3 of process A because process A has waited for semaphore A.

[0084] Process information No. 14 shows that as a result of scheduling, process B has gone into “Run” state.

[0085] Process information No. 15 shows that as a result of the return of semaphore A, the inherited priority has been canceled.

[0086] Process information No. 16 shows that as a result of the return of the semaphore, process A has gone into “Ready” state.

[0087] Process information No. 17 and No. 18 show that as a result of scheduling, process A has gone into “Run” state.

[0088] As explained so far, with the embodiment, when specific events concerning the priorities and states of processes have taken place, pieces of specific priority information on the events can be acquired and displayed in list form. More specifically, in debugging a concurrent program, information on the priorities of processes to be debugged, including inheritance, cancellation, and basic priority change, can be recorded as a history and displayed in list form.

[0089] Therefore, with the embodiment, because the behavior of processes in the concurrent program, the change of priority, the cause of priority change, etc. can be recorded and displayed in list form for the user to understand it easily, the user can easily find bugs in the application program resulting from priority inheritance caused by an unexpected behavior of the process. This enables efficient debugging, improving the efficiency of the debugging work.

[0090] (Second Embodiment)

[0091] Hereinafter, a second embodiment of the present invention will be explained. The second embodiment relates to a three-dimensional display of process information including the priority information obtained in the first embodiment.

[0092] In this embodiment, the process information including priority information is expressed by three-dimensional coordinates using three coordinate axes consisting of time (t), process (n), and priority (p). In this case, the coordinate system (t, n, p) is referred to as W. For example, when there are three processes (A, B, C) to be displayed, it is assumed that the n-coordinate of process A is 1, the n-coordinate of process B is 2, and the n-coordinate of process C is 3. When the priority of a process to be displayed is P. the p-coordinate is assumed to be [−P]. The reason for this is that the present embodiment is intended for a system where the value of the priority of a process whose priority is high is smaller than that of the priority of a process whose priority is low. At time T when an event to be displayed has occurred, the t-coordinate is determined to be T. A three-dimensional coordinate system (x, y, z) for output is determined to be D.

[0093] As shown in FIG. 14, the priority information display system of the present embodiment comprises an input section 100, a process information analyzing section 101, a coordinate transformation section 102, and an output section 103. Although not shown, the process information analyzing section 101 is connected to the priority information storage section 4 explained in the first embodiment and gets the process information including priority information from the storage section 4.

[0094] The user uses an input section 100 to specify a process to be displayed, a coordinate shift of r, and a rotational angle of a. The process information analyzing section 101 reads the process information on the process to be displayed from all of the process information and creates the W-coordinate information. On the basis of the coordinate shift r and rotational angle α, the coordinate transformation section 102 transforms the W-coordinate information created by the process information analyzing section 101 into the D-coordinate information to be outputted from the output section 103. The output section 103 creates three-dimensional display information from the D-coordinate information and outputs it.

[0095] A series of operations in the display processing in the present embodiment thus constructed will be described. Explanation will proceed taking a case where the user has specified (0, 0, 0) for the coordinate shift r and 0 for the rotational angle α.

[0096] The process information analyzing semiconductor 101 reads pieces of process information to be displayed (No. 1 to No. 17) from the priority information storage section 4 and gets the W-coordinate information as described below.

[0097] Reads in process information No. 1 that the initial state of process A is “Wait.” From this time on, the state of process A is stored as “Wait” until it has been changed.

[0098] Reads in process information No. 2 that the initial state of process B is “Ready.” From this time on, the state of process B is stored as “Ready” until it has been changed.

[0099] Reads in process information No. 3 that the initial state of process C is “Ready.” From this time on, the state of process C is stored as “Ready” until it has been changed.

[0100] Reads in process information No. 4 that the initial basic priority of process A (n=1) is 3 (p=3). Because the process is in the initial state, time t=0 is set and W-coordinate information No. 1 “(0, 1, −3), state Wait” is obtained.

[0101] Reads in process information No. 5 that the initial basic priority of process B (n=2) is 4 (p=4). Because the process is in the initial state, time t=0 is set and W-coordinate information No. 2 “(0, 2, −4), state Ready” is obtained.

[0102] Reads in process information No. 6 that the initial basic priority of process C (n=3) is 5 (p=5). Because the process is in the initial state, time t=0 is set and W-coordinate information No. 3 “(0, 3, −5), state Ready” is obtained.

[0103] Reads in process information No. 7 that process B (n=2) has changed the state to Run. W-coordinate information No. 4 “(0, 2, −4), state Run” is obtained.

[0104] Reads in process information No. 8 that process B has caused process A (n=1) to change the state to Ready. Because the first event has occurred, time t=1 is set and W-coordinate information No. 5 “(1, 1, −3), state Ready, state change causing process B” is obtained. Furthermore, W-coordinate information No. 6 “(1, 2, −4), process A state change” is obtained.

[0105] Reads in process information No. 9 that process B (n=2) has changed the state to Ready. W-coordinate information No. 7 “(1, 2, −4), state Ready” is obtained.

[0106] Reads in process information No. 10 that process A (n=1) has changed the state to Run. W-coordinate information No. 8 “(1, 1, −3), state Run” is obtained.

[0107] Reads in process information No. 11 that process A has caused process B (n=2) to change the basic priority to 6. Because the second event has occurred, time t=2 is set and W-coordinate information No. 9 “(2, 2, −3), state Ready” and W-coordinate information No. 10 “(2, 2, −6), state Ready, priority change causing process A” are obtained. Furthermore, W-coordinate information No. 11 “(2, 1, −3), priority-changed process B is obtained.

[0108] Reads in process information No. 12 that semaphore A has caused process A (n=1) to change the state to Wait. Because the third event has occurred, time t=3 is set and W-coordinate information No. 12 “(3, 1, −3), state Wait, causal semaphore A” is obtained.

[0109] Reads in process information No. 13 that process A has caused process B (n=2) to inherit the priority. W-coordinate information No. 13 before inheritance of the value of the priority “(3, 2, −6), state Ready, before priority inheritance” and W-coordinate information No. 14 “(3, 2, −3), state Ready; process A priority inheritance” are obtained. From this time on, the priority inheritance state of process A and the before-inheritance priority 6 are stored as the priority state of process B.

[0110] Reads in process information No. 14 that process B (n=2) has changed the state to Run. W-coordinate information No. 15 “(3, 2, −3), state Run” is obtained.

[0111] Reads in process information No. 15 that semaphore A has caused process B (n=2) to cancel the inheritance of the priority. Because the fourth event has occurred, time t=4 is set and W-coordinate information No. 16 before the change of the priority value “(4, 2, −3), state Run, before cancellation of semaphore A priority inheritance” and W-coordinate No. 17 “(4, 2, −6), state Run, cancellation of semaphore A priority inheritance” are obtained.

[0112] As a result of the above-described processes, the following W-coordinate information is obtained. W-coordinate information No. 1: process A, (0, 1, −3), state Wait

[0113] W-coordinate information No. 2: process B, (0, 2, −4), state Ready

[0114] W-coordinate information No. 3: process C, (0, 3, −5), state Ready

[0115] W-coordinate information No. 4: process B, (0, 2, −4), state Run

[0116] W-coordinate information No. 5: process A, (1, 1, −3), state Ready, causal process B

[0117] W-coordinate information No. 6: process B, (1, 2, −4), process A state change

[0118] W-coordinate information No. 7: process B, (1, 2, −4), state Ready

[0119] W-coordinate information No. 8: process A, (1, 1, −3), state Run

[0120] W-coordinate information No. 9: process B, (2, 2, −3), state Ready

[0121] W-coordinate information No. 10: process B, (2, 2, −6), state Ready, priority change causing process A

[0122] W-coordinate information No. 11: process A, (2, 1, −3), priority-changed process B

[0123] W-coordinate information No. 12: process A, (3, 1, −3), state Wait, causal semaphore A

[0124] W-coordinate information No. 13: process B, (3, 2, −6), state Ready, before priority inheritance

[0125] W-coordinate information No. 14: process B, (3, 2, −3), state Ready, process A priority inheritance

[0126] W-coordinate information No. 15: process B, (3, 2, −3), state Run

[0127] W-coordinate information No. 16: process B, (4, 2, −3), state Run, before cancellation of semaphore A priority inheritance

[0128] W-coordinate information No. 17: process B, (4, 2, −6), state Run, cancellation of semaphore A priority inheritance

[0129] Then, according to the rotational operation Rα on the basis of the coordinate shift r and the rotational angle α, the coordinate transformation section 102 transforms the W-coordinate information created at the process information analyzing section 101 into D-coordinate information to display the data on the output section 103. In the embodiment, it is assumed that the D-coordinate system has the same origin of (0, 0, 0) as that of the W-coordinate system and is a three-dimensional coordinate system using (−1, 1, 0) as an x-axis vector, (−1, −1, 2) as a y-axis vector, and (1, 1, 1) as a z-axis vector.

[0130] A transformation matrix WD from the W-coordinate system into the D-coordinate system is expressed by the following equation (1): ${\left[\begin{array}{ccc}-\frac{1}{\sqrt{2}}& -\frac{1}{\sqrt{6}}& \frac{1}{\sqrt{3}}\\ \frac{1}{\sqrt{2}}& -\frac{1}{\sqrt{6}}& \frac{1}{\sqrt{3}}\\ 0& \frac{2}{\sqrt{6}}& \frac{1}{\sqrt{3}}\end{array}\right]}^{-1}$

[0131] The coordinate transformation section 102 transforms point w on the W-coordinate system into point d on the D-coordinate system using the following equation (2):

[0132] d=WDRαw+r  (2)

[0133] Hereinafter, the coordinate obtained by transforming coordinate wx in W-coordinate information No. x is expressed as dx. As a result of the transformation, the following pieces of information are obtained:

[0134] D-coordinate information No. 1: process A, d1, state Wait

[0135] D-coordinate information No. 2: process B, d2, state Ready

[0136] D-coordinate information No. 3: process C, d3, state Ready

[0137] D-coordinate information No. 4: process B, d4, state Run

[0138] D-coordinate information No. 5: process A, d5, state Ready, causal process B

[0139] D-coordinate information No. 6: process B, d6, process A state change

[0140] D-coordinate information No. 7: process B, d7, state Ready

[0141] D-coordinate information No. 8: process A, d8, state Run

[0142] D-coordinate information No. 9: process B, d9, state Ready

[0143] D-coordinate information No. 10: process B, d10, state Ready, priority change causing process A

[0144] D-coordinate information No. 11: process A, d11, priority changed process B

[0145] D-coordinate information No. 12: process A, d12, state Wait, causal semaphore A

[0146] D-coordinate information No. 13: process B, d13, state Ready, before priority inheritance

[0147] D-coordinate information No. 14: process B, d14, state Ready, process A priority inheritance

[0148] D-coordinate information No. 15: process B, d15, state Run

[0149] D-coordinate information No. 16: process B, d16, state Run, before cancellation of semaphore A priority inheritance

[0150] D-coordinate information No. 17: process B, d17, state Run, cancellation of semaphore A priority inheritance

[0151] Then, the output section 103 projects the d-coordinate information on the z=0 plane in parallel with the z-axis.

[0152] Here, processing is effected by the type of process as described below.

[0153] D-coordinate information No. 1: process A, d1, state Wait

[0154] D-coordinate information No. 5: process A, d5, state Ready, causal process B

[0155] D-coordinate information No. 8: process A, d8, state Run

[0156] D-coordinate information No. 11: process A, d11, priority changed process B

[0157] D-coordinate information No. 12: process A, d12, state Wait, causal semaphore A

[0158] D-coordinate information No. 2: process B, d2, state Ready

[0159] D-coordinate information No. 4: process B, d4, state Run

[0160] D-coordinate information No. 6: process B, d6, process A state change

[0161] D-coordinate information No. 7: process B, d7, state Ready

[0162] D-coordinate information No. 9: process B, d9, state Ready

[0163] D-coordinate information No. 10: process B, d10, state Ready, priority change causing process A

[0164] D-coordinate information No. 13: process B, d13, state Ready, before priority inheritance

[0165] D-coordinate information No. 14: process B, d14, state Ready, process A priority inheritance

[0166] D-coordinate information No. 15: process B, d15, state Run

[0167] D-coordinate information No. 16: process B, d16, state Run, before cancellation of semaphore A priority inheritance

[0168] D-coordinate information No. 17: process B, d17, state Run, cancellation of semaphore A priority inheritance

[0169] D-coordinate information No. 3: process C, d3, state Ready

[0170] According to the D-coordinate information created by the above-mentioned processes, a three-dimensional image of the priority information is outputted. Hereinafter, the procedure for creating (outputting) the three-dimensional image will be described.

[0171] First, the processing concerning process A is done as follows:

[0172] According to information No. 1, “process A” and priority value “3” are outputted to d1.

[0173] According to information No. 1 and No. 5, a line representing Wait is outputted in the range from d1 to d5.

[0174] According to information No. 5 and No. 8, a line representing Ready (which takes the form of a dotted line) is outputted in the range from d5 to d8.

[0175] According to information No. 8 and No. 12, a line representing Run is outputted in the range from d6 to d5.

[0176] According to information No. 5 and No. 6, a line representing process control is outputted in the range from d6 to d5.

[0177] According to information No. 12, “semaphore A” is outputted to d12.

[0178] Then, the processing concerning process B is effected as described below.

[0179] According to information No. 2, “process B” and the priority value 141 are outputted to d2.

[0180] According to information No. 2 and No. 4, a line representing Ready (which takes the form of a dotted line) is outputted in the range from d2 to d4.

[0181] According to information No. 4 and No. 7, a line representing Run is outputted in the range from d4 to d7.

[0182] According to information No. 7 and No. 9, a line representing Ready is outputted in the range from d7 to d9.

[0183] According to information No. 9 and No. 10, a line representing Ready is outputted in the range from d9 to d10.

[0184] According to information No. 10 and No. 13, a line representing Ready is outputted in the range from d10 to d13.

[0185] According to information No. 13 and No. 14, a line representing priority is outputted in the range from d13 to d14.

[0186] According to information No. 14 and No. 15, a line representing Run is outputted in the range from d14 to d15.

[0187] According to information No. 15 and No. 16, a line representing Run is outputted in the range from d15 to d16.

[0188] According to information No. 15 and No. 16, a line representing priority is outputted in the range from d16 to d17.

[0189] According to information No. 10, the priority value “6” is outputted to d10.

[0190] Although according to information No. 5 and No. 6, a line representing process control can be outputted in the range from d6 to d5, the line will not be outputted because the line has already been outputted in the processing concerting process A.

[0191] According to information No. 14 and No. 12, a line representing priority inheritance is outputted in the range from d14 to d12.

[0192] Then, the processing concerning process C is performed. Specifically, in the processing, according to information No. 3, “process C” and the priority value “5” are outputted to d3.

[0193] As described above, the priority information display system of the second embodiment produces a three-dimensional image of priority information as shown in FIG. 15. In FIG. 15 (−3, −1, 7) is specified for the coordinate shift r by the user. The image enables the user to intuitively grasp the information on the process changing with time, including priority inheritance, cancellation, and process state change. In FIG. 15, a bold line represents the Run state of the process, a fine broken line represents the Ready state, and a denser fine broken line represents the Wait state. A broken-line arrow represents priority inheritance and a bold-line arrow represents process control. To make it easier to grasp the priority inheritance state, colored representation (hatching representation) is used. For instance, in the case of process B, it can be seen easily from the dense hatching that process B is in the priority inheritance state during the period of time during which the priority value remains at 3 (during the same period, the basic priority value remains at 6).

[0194] While in the above-described example, priority inheritance has taken place between process A and process B, a single process may inherit the priorities from a plurality of processes. FIG. 16 illustrates an example of display in such a case. As shown in the figure, the region indicated by R1 represents the state of priority inheritance from process C (a priority value of 5), and the region indicated by R2 represents the state of priority inheritance from process B (a priority value of 3). The R1 and R2 are hatched (colored) differently from each other, which enables the user to grasp the detailed information on priority inheritance.

[0195] As described until now, with the present invention, when a specific event related to the priorities of processes has taken place, not only specific process information on the event can be acquired and displayed in list form, but also the behavior of processes in a concurrent program, the change of priority, the cause of priority change, etc. can be recorded and displayed in list form to the user, so that the user can easily find bugs or the like in the application program stemming from priority inheritance caused by an unexpected behavior of the process. Therefore, it is possible to provide a priority information display system that displays the program information effective in debugging the concurrent program.

[0196] Furthermore, with the present invention, it is possible to provide a priority information display system that displays the priority information three-dimensionally to offer the user more effective priority information.

[0197] Additional advantages and modifications will readily occur to those skilled in the art. Therefore, the present invention in its broader aspects is not limited to the specific details, representative devices, and illustrated examples shown and described herein. Accordingly, various modifications may be made without departing from the spirit or scope of the general inventive concept as defined by the appended claims and their equivalents.