WO2006070510A1

WO2006070510A1 - Program debug device, program debug method, and information storage medium

Info

Publication number: WO2006070510A1
Application number: PCT/JP2005/016492
Authority: WO
Inventors: Atsuhiko Fujimoto
Original assignee: Sony Computer Entertainment Inc.
Priority date: 2004-12-28
Filing date: 2005-09-08
Publication date: 2006-07-06
Also published as: JP2006185360A; TW200634515A

Abstract

There is provided a program capable of effectively performing debug of a program for executing a plurality of processes on a computer. The program for debugging the program executing a plurality of processes on a computer causes the computer to function as a parent-child relationship table storing unit (42) for storing a parent-child relationship table indicating the parent-child relationship of some or all the processes, an instruction object process selection unit (46) for acquiring a process identifier for identifying a process to be debugged and selecting a related process of the process selected by the process identifier acquired, and a command unit (48) for debugging the selected related process.

Description

Program debugging apparatus, program debugging method, and information storage medium

The present invention relates to a program debugging device, a program debugging method, and an information storage medium, and more particularly to a multi-process debugger.

Background art

[0002] A debugger is a computer program for supporting the discovery of a bug (bug) in a computer program. By using a debugger (symbolic debugger), the user can arbitrarily set a breakpoint in the source program and interrupt the execution of the program at the instruction location corresponding to the breakpoint (breakpoint function). In addition, the program can be executed by a fixed amount of processing (for example, one instruction) (step execution function), or the contents of registers and memory can be checked during program execution (watch function ( Or trace function)).

[0003] In particular, in GDB (The GNU Source-Level Debugger) disclosed in Non-Patent Document 1 below, some or all of a plurality of processes executed on a computer are arbitrarily specified, and these are specified. You can interrupt the execution of processes or resume their execution.

Non-Patent Document 1: Richard Stallman, Polish Pesch, Stan Chebbs et al., Debugging with GDB ", [online], March 2000, [Searched December 21, 2000], Internet ~~ net URL : nttp: //www.asahi— net.or.jp/ wg5k— ickw / html / online / gdb— 5.0 / gdb-ja —toc.html>

Disclosure of the invention

Problems to be solved by the invention

However, if a conventional debugger is used to debug a program in which a plurality of processes are executed on a computer, there are the following problems. In other words, when a breakpoint is set in a process, the execution of the same process is simply interrupted at the instruction location corresponding to the breakpoint, or the execution of all the processes being executed is interrupted. It will be interrupted. For this reason, if there is a defect in the child process of the process that set the breakpoint, it is difficult to find the defect anyway.

[0005] The present invention has been made in view of the above problems, and an object of the present invention is to provide a program debugging apparatus and program debugging capable of efficiently performing a debugging operation of a program in which a plurality of processes are executed on a computer. It is to provide a method and an information storage medium.

Means for solving the problem

[0006] In order to solve the above problems, a program debug device according to the present invention is a program debug device for performing debug processing on a program that executes a plurality of processes on a computer, A parent-child relationship table storage unit for storing a parent-child relationship table indicating a part or all of the parent-child relationship of the process; and a process identification information acquisition unit for acquiring process identification information for identifying the process to be debugged. Based on the parent-child relationship table, a related process selection means for selecting a related process of the process identified by the process identification information acquired by the process identification information acquisition means, and a selection by the related process selection means Debug processing means for performing the debug processing on an associated process. The features.

[0007] Further, a program debugging method according to the present invention is a program debugging method for performing a debugging process on a program that executes a plurality of processes on a computer, and includes a part or all of the plurality of processes. Based on the parent-child relationship table, a parent-child relationship table step for storing a parent-child relationship table in the storage means, a process identification information acquisition step for acquiring process identification information for identifying the process to be debugged, and the parent-child relationship table For the related process selection step for selecting a related process of the process identified by the process identification information acquired in the process identification information acquisition step, and for the related process selected in the related process selection step, A debugging process step for performing a debugging process. It is characterized by that.

[0008] Furthermore, an information storage medium according to the present invention is a program for performing a debugging process on a program that executes a plurality of processes, and a part of the plurality of processes or Based on the parent-child relationship table storage means for storing a parent-child relationship table indicating all parent-child relationships, a process identification information acquisition means for acquiring process identification information for identifying the process to be debugged, and the parent-child relationship table, The related process selection means for selecting a related process of the process identified by the process identification information acquired by the process identification information acquisition means, and the debug process for the related process selected by the related process selection means. This is an information storage medium for causing a computer to function as a debugging processing means for performing the above.

[0009] According to the present invention, a parent-child relationship table indicating a parent-child relationship of some or all of a plurality of processes executed by a program to be debugged is stored. Then, process identification information for identifying a process to be debugged is acquired, and a related process of the process identified by the process identification information is selected based on the parent-child relationship table. At this time, based on the parent-child relationship table, the process identified by the process identification information acquired by the process identification information acquisition means, and the direct and indirect child processes of the process may be selected as related processes. Good. Then, debug processing is performed for the selected related process. In this way, not only the process identified by the process identification information but also the related process selected based on the parent-child relationship table can be debugged, and the debugging work can be made efficient. I'll do it.

In one aspect of the present invention, the debugging process is a process for stopping or restarting execution of a related process selected by the related process selection unit. In this way, execution of related processes can be stopped or restarted in a batch.

[0011] Further, in one aspect of the present invention, parent-child relationship data indicating a parent-child relationship of a process being executed on the computer among the plurality of processes is acquired, and the parent-child relationship data is acquired based on the parent-child relationship data. It further includes parent-child relationship updating means for updating the parent-child relationship table stored in the relationship table storage means. In this way, the parent-child relationship table can be updated based on the parent-child relationship of the processes currently running on the computer.

[0012] In this aspect, the parent-child relationship update means obtains parent-child relationship data indicating the parent-child relationship of the process when a process is newly generated on the computer. In addition, the parent-child relationship table stored in the parent-child relationship table storage means may be updated based on the parent-child relationship data. In this way, the parent-child relationship table can be quickly updated when a new process is created.

[0013] Further, according to one aspect of the present invention, when the process already executed on the computer disappears, the parent-child relationship update unit stores data related to the process in the parent-child relationship table storage unit. Deleted from the parent-child relationship table. In this way, when the process disappears, the parent-child relationship table can be quickly updated.

[0014] In one aspect of the present invention, the process identification information acquisition unit acquires process identification information included in a command related to the debug process input by a user. In this way, according to the input of the instruction by the user, it is possible to perform the debugging process on the process related to the process identified by the process identification information included in the instruction.

In one aspect of the present invention, the process identification information acquisition unit acquires process identification information for identifying a process related to a specific type of event that occurs on the computer. In this way, according to the occurrence of a specific type of event, the debugging process can be performed on the related process of the process related to the event.

Brief Description of Drawings

FIG. 1 is a diagram showing a program development environment according to an embodiment of the present invention.

FIG. 2 is a functional block diagram showing functions realized by a debug agent program in a target computer.

FIG. 3 is a functional block diagram of a debug process management unit.

FIG. 4 is a diagram showing an example of a parent-child relationship of a plurality of processes being executed on a target computer.

FIG. 5 is a diagram showing a parent-child relationship table showing parent-child relationships of a plurality of processes shown in FIG.

FIG. 6 is a flowchart showing parent-child relationship registration processing.

FIG. 7 is a flowchart showing debugging processing.

FIG. 8 is a flowchart showing a multi-process instruction process. FIG. 9 is a flowchart showing event processing.

BEST MODE FOR CARRYING OUT THE INVENTION

Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a diagram showing an example of a program development environment according to an embodiment of the present invention. This program development environment 10 applies a program debugging method according to an embodiment of the present invention, and includes a target computer 12 and a host computer 14 that are communicably connected by a data communication network (not shown). Yes. The target computer 12 is a computer that functions as a program debugging apparatus according to an embodiment of the present invention, and the host computer 14 is a computer for debugging a program executed on the target computer 12. These computers can be configured using, for example, a known personal computer system or a workstation.

In the target computer 12, an OS (operating system) 20 is operating, and a user application program 16 and a debug agent program 18 are installed. Then, the user application program 16 and the debug agent program 18 are executed on the OS 20. The user application program 16 is a program that executes a plurality of processes, and is a target of user debugging work. The debug agent program 18 is a kind of application program that runs on the OS 20, operates according to the control from the host computer 14, and transmits various types of debugging data obtained from the OS 20 to the host computer 14. It has become. OS20 includes various debugging programs, and debug agent program 18 uses these programs to debug user application program 16 (execution of each process is suspended, execution resumed, contents of memory and registers). Confirmation, etc.). Each program may be stored and distributed in a computer-readable information storage medium such as a CD-ROM or DVD-ROM. In this case, each program of the information storage medium is read and installed in the target computer 12 or the host computer 14.

[0020] In the host computer 14, an OS 22 is operating, and a debug communication program is executed on the OS 22. The program 24 and the host debugger program 26 are executed. The host debugger program 26 is a kind of application program for debugging the user application program 16, and designates part or all of the processes started by the user application program 16 and interrupts the execution thereof. And can resume execution. In addition, a breakpoint can be set at an arbitrary instruction location of the user application program 16, data can be written to the memory or register of the target computer 12, and the corresponding data can be read, process list acquisition and process status information can be obtained. You can get it. Furthermore, the debug agent program 18 monitors the arrival of breakpoints (hit events) set in the user application program 16, the occurrence of program exceptions, and the end of step execution. If these events occur, the host debugger program 26 is notified of the data indicating them. The host debugger program 26 displays various data thus notified on a display or the like.

[0021] The debug communication program 24 relays data communication between the host debugger program 26 and the debug agent program 18, and converts the data of the host debugger program 26 into data that can be processed by the debug agent program 18. Conversely, the data of the debug agent program 18 is converted into data that can be processed by the host debugger program 26.

Here, a functional configuration of the debug agent program 18 will be described. FIG. 2 is a functional block diagram showing functions realized by the debug agent program 18 on the target computer 12. The debug agent program 18 is executed by the target computer 12 to realize the functions of the debug protocol transmission / reception block 28, the process control block 30, the debug processing block 32, and the event processing block 34. The debug protocol transmission / reception block 28 includes a transmission unit 28a, a protocol encoding unit 28b, a reception unit 28c, and a protocol decoding unit 28d. The process control block 30 includes a command analysis unit 30a and a debug process management unit 3 Ob. The debug processing block 32 includes a static information processing unit 32a and an execution control unit 32b. First, the debug protocol transmission / reception block 28 is executed on the host computer 14 via the data communication network to communicate with the debug communication program 24. Specifically, the protocol encoding unit 28 b converts the processing result passed from the debug processing block 32 into data that can be interpreted by the debug communication program 24. The transmission unit 28a transmits the processing result of the debug processing block 32 encoded by the protocol encoding unit 28b to the debug communication program 24. The host debugger program 26 displays the processing result transmitted to the debug communication program 24 in this way. The receiving unit 28c receives data transmitted from the debug communication program 24. This data is input from the host debugger program 26, and indicates an execution interruption instruction, an execution restart instruction, a memory read instruction, a register read instruction, and the like. The execution suspension instruction and the execution resume instruction include a process ID (identification information) for identifying a process to be suspended or resumed. The protocol decoding unit 28d converts the data received by the receiving unit 28c into data that can be interpreted by the process control block 30. The converted data is passed to the process control block 30.

The process control block 30 analyzes the data passed from the debug protocol transmission / reception block 28 and issues a debug instruction corresponding to the instruction indicated by the data to the debug processing block 32. Specifically, the command analysis unit 30a analyzes the data passed from the protocol decoding unit 28d, and whether the instruction indicated by the data is an execution interruption instruction, an execution restart instruction, a memory read instruction, a register read instruction, or the like Judging. If it is a memory read instruction or a register read instruction, a debug instruction corresponding to the instruction is issued to the debug processing block 32 as it is. On the other hand, if it is an execution interruption instruction or an execution resumption instruction, the contents of those instructions are passed to the debug process management unit 30b.

[0025] The debug process management unit 30b checks a process ID included in the execution suspension instruction and the execution restart instruction in a parent-child relation table described later, and selects a related process of the process identified by the process ID. This related process is specifically all direct or indirect child processes. The debug process management unit 30b outputs a debug instruction for suspending or resuming execution of the related process (including a process identified by the process ID included in the execution suspend instruction or execution resume instruction) selected in this way. Issued against.

The debug processing block 32 executes debug processing according to the debug instruction issued by the command analysis unit 30a or the debug processing block 32. That is, the static information processing unit 32a reads the memory and the register in accordance with the debug instruction issued by the command analysis unit 30a, and passes the contents to the protocol encoding unit 28b of the debug protocol transmission / reception block 28. The execution control unit 32b suspends execution or resumes execution of a plurality of processes according to the debug instruction issued by the debug processing block 32.

[0027] The event processing block 34 detects the occurrence of a specific event in the OS 20. Here, the specific event is a thread creation event, a thread disappearance event, a process creation event, a process disappearance event, or the arrival of an instruction point corresponding to a breakpoint set in the user application program 16 in advance (break hit Event), program exception, and step execution end event. When the occurrence of a thread creation event or a thread disappearance event is detected, the fact is passed to the debug protocol transmission / reception block 28. As a result, the occurrence of these events is notified to the host computer 14 (more specifically, the host debugger program 26). On the other hand, when the occurrence of the process generation event is detected, the fact is passed to the debug process management unit 30b of the process control block 30. As a result, management of the parent-child relationship of the newly generated process is started by the debug process management unit 30b. When the occurrence of a process extinction event is detected, that fact is passed to the debug process management unit 30b. As a result, management of the parent-child relationship of the extinguished process is terminated in the debug process management unit 30b. When the occurrence of a break hit event is detected, a process execution interruption instruction including the PID (process ID) of the process in which the breakpoint related to the hit event is set is passed to the debug process management unit 30b. Debug process management unit 3 Ob determines which process should be interrupted based on the parent-child relationship table, and issues debug instructions to debug processing block 32 to interrupt the execution of those processes. . When a program exception is detected, the exception handler included in OS20 is executed. When a step execution end event is detected, a process execution interruption instruction including the PID of the process related to the step execution end event is passed to the debug process management unit 30b. The debug process management unit 30b is based on the parent-child relationship table. The process determines which process should be interrupted and issues a debug instruction to the debug processing block 32 to interrupt the execution of those processes.

Here, the debug process management unit 30b will be further described with reference to FIG.

As shown in the figure, the debug process management unit 30b includes a parent-child relationship table update unit 40, a parent-child relationship table storage unit 42, an instruction issue process list storage unit 44, an instruction target process selection unit 46, and an instruction unit 48. It has been. The parent-child relationship table storage unit 42 includes the memory of the target computer 14 and stores a parent-child relationship table indicating the parent-child relationship of the process to be debugged. FIG. 4 is a diagram illustrating an example of a parent-child relationship of a plurality of processes being executed on the target computer 12, and FIG. 5 is a diagram illustrating a parent-child relationship table indicating a parent-child relationship. As shown in Fig. 5, the parent-child relationship table stores the management target PID, the parent process PID, and the child process PID in association with each other. The managed PID is identification information (PID) that identifies the process that manages the parent-child relationship, that is, the process that is being debugged. The parent process PID is identification information (PID) that identifies the parent process of the process identified by the corresponding managed PID. If the parent process does not exist or is not known, a null value (indicated by a horizontal line in the figure) is stored. The child process PID is identification information (PID) that identifies the child process of the process identified by the corresponding managed PID. If no child process exists or is not found, a null value (indicated by a horizontal line in the figure) is stored.

[0029] When the event processing block 34 notifies the occurrence of a process generation event from the event processing block 34, the parent-child relation table update unit 40 adds a record having the generated process PID as a managed PID to the parent-child relation table. Then, store the PID of the created parent process in the parent process PID column of the record in the parent-child relationship table. Also, a null value is stored in the child process PID column of the same record. Furthermore, the PID of the created process is referred to as the management target PID and the registered record is referenced, and the PID of the created process is stored in the child process PID column. The above processing will be described in detail later as parent-child relationship registration processing. When the event processing block 34 notifies the occurrence of a process extinction event, the parent-child relationship table update unit 40 deletes the record having the PID of the extinguished process as the management target PID from the parent-child relationship table. Furthermore, the disappeared professional Delete the PID of the process from the parent process PID column and child process PID column of other records

[0030] When a process execution suspension instruction or a process execution restart instruction is passed from the event processing block 34 or the command analysis section 30a, the instruction target process selection section 46 directly processes the process identified by the PID included in those instructions. Read PID of child process from parent-child relationship table. Further, the PID of the direct child process of the process identified by the read PID (indirect child process as viewed from the process identified by the original PID) is read from the parent-child relationship table. By repeating this process, PID can be obtained for all direct or indirect child processes. These PIDs are sequentially stored in an instruction issue process list storage unit 44 that includes the memory of the target computer 12. The instruction unit 48 reads the PIDs stored in the instruction issue process list storage unit 44, and processes execution interruption instructions or processes passed from the event processing block 34 or the command analysis unit 30a to the processes identified by these PIDs. A debug instruction is issued to debug processing block 32 to execute the resume execution instruction. In this way, when a process execution interruption instruction is passed from the event processing block 34 or the command analysis unit 30a, the execution of all direct or indirect child processes of the process identified by the PID included in those instructions is interrupted. be able to. In addition, when a process execution resumption instruction is passed from the command analysis unit 30a, it is possible to resume the execution of all direct or indirect child processes of the process identified by the PID included in the instruction.

Here, the main processing of the debug agent program 18 will be described based on a flowchart. FIG. 6 is a flowchart showing a parent-child relationship registration process by the debug agent program 18. The parent-child relationship registration process shown in the figure is executed by the parent-child relationship table update unit 40 included in the debug process management unit 30b when it is notified from the event processing block 34 that a process generation event has been detected. Is. In this process, event information of a process generation event is first acquired (S101). The event information includes the PID of the generated process, and it is checked whether this PID is already stored in the management target PID column of any record in the parent-child relationship table (S102). If it is stored, the parent-child relationship registration process is terminated. On the other hand, if not remembered In S101, the OS 20 is inquired and acquired for the PID parent-child relationship data included in the acquired event information (S103). The parent-child relationship data includes the PID of the parent process and the child process identified by the PID included in the event information acquired in S101. Then, it is checked whether the PID of the parent process included in the parent-child relationship data is already stored in the management target PID column of any record in the parent-child relationship table (S104). If it is stored, the PID included in the event information acquired in S101 is stored in the child process PID column of the record (S105). If not stored, this S105 process is skipped. Finally, a new record is added to the parent-child relationship table, and the PID included in the event information acquired in the management target PID field S101 is stored. At this time, null values are stored in the parent process column and the child process column.

[0032] As described above, when a process is newly generated, the parent-child relationship regarding the process can be stored in the parent-child relationship table.

Next, FIG. 7 is a flowchart showing debugging processing by the debug agent program 18. This process is executed when a debug instruction is input from the host debugger program 26 and the debug instruction is transmitted to the debug agent program 18 by the debug communication program 24. As shown in the figure, in this process, the receiving unit 28c first receives a debug instruction (S201), and the protocol decode unit 28d decodes the debug instruction (S202). Next, the command analysis unit 30a analyzes the decoded debug instruction and acquires the type of the instruction (S203). At this time, if the type of instruction is a specific one, that is, if it is a process execution interruption instruction or an execution resumption instruction (S204), multiple process instruction processing is executed (S205). With this process, the debug instruction is de-processed so that the execution suspension process or the execution restart process is executed for all direct or indirect child processes of the process identified by the PID included in the execution suspension instruction or the execution resume instruction. Issued to bag processing block 32. On the other hand, if the instruction type is not specific, the instruction contents inputted from the host debugger program 26 are not changed, and the debug instruction is issued to the debug processing block 32 (S206). Thereafter, the protocol encoding unit 28b decodes the processing result of the debug instruction (S207), and the transmission unit 28a transmits it to the host computer 14. [0034] According to the above processing, in particular, when a process execution interruption instruction or execution resumption instruction is input to the host debugger program 26, not only the process identified by the PID included in those instructions but also its process directly. Alternatively, execution interruption processing or execution resumption processing is executed for all indirect child processes.

FIG. 8 is a flowchart showing multi-process instruction processing by the debug agent program 18. The processing shown in the figure is executed in S205 in FIG. 7 and S403 in FIG. As shown in FIG. 8, in this process, first, the PID of the process to be directly commanded is acquired (S301). Then, the record in which the PID is stored in the management target PID column is read from the parent-child relationship table, and the child process PID column force also reads the PID (S302). These PIDs are stored in the instruction issue process list storage unit 44 (S303). Further, it is checked whether or not the record in which the PID stored in the instruction issue process list storage unit 44 is stored in the parent process PID column exists in the parent-child relationship table (S304). If there is such a record, the PID is acquired from the child process PID column of the record, and additionally stored in the instruction issue process list storage unit 44 (S305). In this case, the process of S304 is executed again. If it is determined in S304 that there is no record, the command unit 48 issues a process execution interruption command or a process execution restart command for the PID stored in the command issuing process list 44 (S306).

[0036] According to the above processing, when a certain PID is acquired, the PID can be surely acquired for all direct or indirect child processes of the process identified by the PID. it can.

Finally, FIG. 9 is a flowchart showing event processing by the debug agent program 18. The processing shown in the figure is executed centering on the event processing block 34. When an event occurrence is detected (S401), it is determined whether or not it is a specific event (S402). If the event is a specific event, that is, a break hit event or a step execution end event, the debug process management unit 30b is caused to execute the multi-process instruction processing shown in FIG. 8 (S403). Thereafter, the debug processing block 32 acquires the result of the instruction, and the protocol encoding unit 28b encodes it (S404). Then, the encoded instruction result is transmitted to the host computer 14 (S405). Meanwhile, in S402 If it is determined that the event is not a specific event, the event processing block 34 notifies the protocol encoding unit 28b of the event occurrence. As a result, the protocol encoding unit 28b encodes data indicating the occurrence of an event, and the transmission unit 28a transmits the data to the host computer 14 (S406).

[0038] According to the above processing, if a break hit event or a step execution end event occurs in OS20, all direct or indirect child processes of the process related to those events will be ignored. Execution can be interrupted.

In the embodiment described above, a parent-child relationship table indicating a parent-child relationship of some or all of a plurality of processes executed by the program to be debugged is stored in the parent-child relationship table storage unit 42. Then, a PID for identifying the process to be debugged is acquired, and all direct or indirect child processes of the process identified by this PID are selected based on the parent-child relationship table. Then, a debugging process is performed for the selected processes. Thus, according to the present embodiment, not only the process identified by the acquired P ID but also all direct or indirect child processes selected based on the parent-child relationship table can be debugged. This makes debugging work more efficient.

[0040] It should be noted that the present invention is not limited to the above-described embodiment, and various modifications can be made. For example, in the above description, the host debugger program 26 is executed on the host computer 14 different from the target computer 12. The host debugger program 26 or an equivalent program may be executed on the target computer 12. Good. In this way, you can debug the program on one computer.

Claims

The scope of the claims

[1] A program debugging apparatus for performing debugging processing on a program that executes a plurality of processes on a computer,

A parent-child relationship table storage means for storing a parent-child relationship table showing a parent-child relationship of all or part of the plurality of processes;

Process identification information acquisition means for acquiring process identification information for identifying a process to be debugged;

A related process selection means for selecting a related process of the process identified by the process identification information acquired by the process identification information acquisition means based on the parent-child relationship table;

Debug processing means for performing the debug processing on the related process selected by the related process selection means;

A program debugging apparatus comprising:

[2] In the program debugging device according to claim 1,

The debugging process is a process for stopping or resuming execution of a related process selected by the related process selection means.

A program debugging apparatus.

[3] In the program debugging device according to claim 1 or 2,

The parent-child relationship data indicating the parent-child relationship of a process being executed on the computer among the plurality of processes is acquired, and the parent-child relationship table stored in the parent-child relationship table storage means based on the parent-child relationship data is acquired. It further includes a parent-child relationship update method to be updated,

A program debugging apparatus.

[4] In the program debugging device according to claim 3,

The parent-child relationship updating means acquires parent-child relationship data indicating a parent-child relationship of the process when a process is newly generated on the computer, and stores the parent-child relationship table based on the parent-child relationship data. Updating the parent-child relationship table stored in the means; A program debugging apparatus.

[5] In the program debugging device according to claim 3,

The parent-child relationship updating means has already been executed on the computer! When a process to be extinguished disappears from the parent-child relationship table stored in the parent-child relationship table storage means, data relating to the process;

A program debugging apparatus.

[6] In the program debugging device according to claim 1,

The process identification information acquisition means acquires process identification information included in an instruction related to the debug process input by a user;

A program debugging apparatus.

[7] In the program debugging device according to claim 1,

The process identification information acquisition means acquires process identification information for identifying a process related to a specific type of event generated on the computer.

A program debugging apparatus.

[8] In the program debugging device according to claim 1,

The related process selection means, based on the parent-child relationship table, processes identified by the process identification information acquired by the process identification information acquisition means, and direct and indirect child processes of the process as the related processes. A program debugging device characterized by being selected.

[9] A program debugging method for performing debugging on a program that executes a plurality of processes on a computer,

A parent-child relationship table step of storing in a storage means a parent-child relationship table indicating a parent-child relationship of all or part of the plurality of processes;

A process identification information acquisition step for acquiring process identification information for identifying a process to be debugged;

A related process selection step for selecting a related process of the process identified by the process identification information acquired in the process identification information acquisition step based on the parent-child relationship table; A debug process step for performing the debug process on the related process selected in the related process selection step;

A program debugging method comprising:

A computer-readable information storage medium storing a program for performing debug processing on a program executing a plurality of processes,

A related process selection means for selecting a related process of the process identified by the process identification information acquired by the process identification information acquisition means based on the parent-child relationship table; and

Debug processing means for performing the debug processing on the related process selected by the related process selecting means

A computer-readable information storage medium storing a program for causing a computer to function as a computer.