JP2003303115A - Device, method, and program for setting breakpoint - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a breakpoint setting device setting a breakpoint without requiring manual operation by a programmer. <P>SOLUTION: This breakpoint setting device is provided with a correction line list management part 115 managing a position on a source program about an edited part and a breakpoint setting/releasing part 106 setting the breakpoint in the position managed by the correction line list management part 115. When the breakpoint is automatically set in the part edited by the programmer, instructions for setting of the breakpoint, designation of the setting position, and the like by the programmer can be omitted, and consequently, an operation load of the programmer can be lowered. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to improvement of a breakpoint setting function in a debugger tool used for program development.

[0002]

2. Description of the Related Art A debugger is used as software that assists in finding and correcting defects in programs. The debugger has a function of stopping the execution at an appropriate position on the source code, a function of outputting the content of the variable at the time of the stop, etc. (for example, refer to Patent Document 1). This stop position is called a breakpoint.

Breakpoints are set by the programmer at correction points on the source code, and many debuggers are devised so that the programmer can easily set the breakpoints on the editor. For example, in the editor where the source code is displayed,
For example, when the programmer puts the mouse pointer on the position where the breakpoint is to be set and clicks, the debugger sets the breakpoint at that position. The position where the break point is set is displayed in the editor with markers such as markers and symbols.

More specifically, the debugger inserts an interrupt instruction or the like at the position of the breakpoint set by the programmer, acquires control at the position of the interrupt instruction or the like, and confirms the value of the variable or the state of the stack. To be able to. When restarting the stopped processing, the debugger removes the interrupt instruction and the like from the source code, restores the original state, and restarts the execution of the program.

[0005]

[Patent Document 1] Japanese Unexamined Patent Publication No. 5-204708

[0006]

As described above, in the conventional debugger, it is necessary for the programmer to set a breakpoint appropriately, which is a burden on the programmer. For example, the procedure for setting a breakpoint at a modified location is to set a breakpoint every time each location is modified, or to set a breakpoint after modifying all locations. However, in the former case, the work of repeating the modification and the breakpoint setting alternately becomes complicated, and in the latter, it is necessary to remember the correction part without forgetting it. Become.

Therefore, it is an object of the present invention to provide a breakpoint setting device for setting a breakpoint without bothering a programmer.

[0008]

In order to solve the above-mentioned problems, a breakpoint setting device of the present invention comprises a loading means for loading an executable program generated based on a source program, and each of the source programs. Storage means for storing information indicating a correspondence relationship between an element and each part constituting the executable program, and a case where the source program is edited,
Acquisition means for acquiring and storing position information indicating to which of the elements constituting the source program the specific edit is made when the edit is specific; and the loaded execution. The formal program includes a setting unit that sets a breakpoint at a position corresponding to an element indicated by the position information acquired by the acquisition unit.

According to this structure, the breakpoint setting device grasps the position of the edited part on the source program by managing the edited part on the source program edited by the editing operation of the operator, Since the breakpoint is set, it is not necessary for the operator to instruct the setting of the breakpoint and the position of the editing point.

Further, each element is each line constituting the source program, and the information stored in the storage means indicates a correspondence relationship between a line number for identifying each line and each location. The acquisition means may be configured to acquire and store, as the position information, a line number of a line in the source program in which a specific edit has been made.

Further, the specific edit includes deletion of a line feed code, and the breakpoint setting device further includes: when the source program is edited,
When the edit content of the edit location is the deletion of the line feed code, the line number of the edit location is stored, and the line number of the line related to the edit is stored among the line numbers already acquired and stored by the acquisition unit. It is also possible to provide an updating unit that rewrites each line number having a large number with a line number having a smaller value by one.

Further, the break point setting device is
Further, in the case where the source program is edited, when the edited content of the edited portion is addition of a line feed code to the beginning of the line, the same line number as the edited portion among the line numbers already acquired and stored by the acquisition means. An updating unit may be provided for rewriting the line number and the line number having a larger value than the line number of the edited part into a line number having a value larger by one.

Further, the break point setting device is
Further, in the case where the source program is edited, if the edited content of the edited part is addition of a line feed code to the end of the line, the line number from the edited part among the line numbers already acquired and stored by the acquisition means. Also, an updating unit for rewriting a row number having a large value into a value having a larger value may be provided.

Further, the specific edit includes addition of a line feed code in the line, and the breakpoint setting device further edits the edited content of the edit location when the source program is edited. When the line feed code is added to the line, each line number having a value larger than the line number of the edit location among the line numbers already acquired and stored by the acquisition unit is written as a value one larger. Alternatively, an updating unit may be provided that newly stores the line number of the edit location and the line number whose value is one greater than the line number of the edit location.

Further, the acquisition means determines, when the source program is edited, whether or not the edited content of the edited portion is editing for a character string other than a line feed code, and the determining means. If the determination is affirmatively determined by, an updating unit that newly stores the line number of the edited location of the edited location may be provided. Further, the acquisition means further stores line range information indicating a range of each control block forming the source program from where on the source program to a line number, and the setting means, A break point may be set at a corresponding position on the executable program corresponding to the top line number of each control block indicated by the line range information.

Further, the setting means does not set the break point of the corresponding portion for the line number after the two consecutive line numbers before and after the line number stored by the acquisition means. It may be configured as follows. Further, the break point setting device creates a bug vote in which information on an edit location corresponding to the break point input by the user for each break point set by the setting means is created, and the bug note is set by the user. It may be presented to the user via an interface.

Further, the break point setting device is
In the creation of the bug slip, the number of times the edited portion is decoded and executed by the debugger may be acquired from the debugger, and the number of times may be included in the information regarding the edited portion and presented. Further, when the position information corresponding to the specific edit has already been acquired and stored, the acquisition unit may prevent the position information from being stored.

Further, the acquisition means further stores line range information indicating a range of each control block forming the source program from a position on the source program to a position on the source program. The means sets, for each of the control blocks, a break point at the beginning of the lines in the control block that have been subjected to the specific editing, and prevents a break point from being set at the other lines.

In the breakpoint setting method, the loading step of loading the execution format program generated based on the source program, the correspondence between each element configuring the source program and each location configuring the execution format program. A storage step of storing information indicating a relationship in a memory, and a case where an edit is made to the source program, and when the edit content is specific, the specific edit constitutes the source program. An acquisition step of acquiring and storing in memory the position information indicating which of each element was performed, and a location corresponding to the element indicated by the position information acquired by the acquisition step in the loaded executable program. And a setting step of setting a breakpoint.

Further, the breakpoint setting program is a program, the program is a loading step of loading an execution form program generated on the basis of a source program into a computer, each element constituting the source program and the execution form program. And a step of storing information indicating a correspondence relationship with each part constituting the memory in a memory, and a case where the source program is edited and the edited content is specific, An acquisition step of acquiring and storing in memory the position information indicating to which of the respective elements configuring the source program the edit has been made; and the position information acquired by the acquisition step in the loaded executable program. Set breakpoints at the locations corresponding to the elements pointed to by Setting step of the may be execution.

[0021]

DESCRIPTION OF THE PREFERRED EMBODIMENTS <First Preferred Embodiment> A debug device according to the present preferred embodiment will be described below with reference to the drawings. FIG. 1 is a block diagram of the debug device according to the first embodiment. In FIG. 1, the debug device 10 includes a command input unit 102 that receives a command input by an operator from the outside, a command analysis unit 103 that analyzes a command,
A make unit 11 that performs a make process, a debugger unit 12 that performs a debug process, and an editor unit 13 that performs an edit process.
Composed of.

The make unit 11 includes an execution file management unit 104 that creates and holds the latest execution file. The debugger unit 12 reads a latest execution file, a load unit 105, a breakpoint setting / cancellation unit 106 that sets / cancels a breakpoint, an execution control unit 107 that controls execution of an executable file, and displays source code on a display or the like. Source code display unit 108, break point display unit 109 for displaying a mark or the like on the break point setting position of the source code and displaying it on a display or the like, break for performing a predetermined process when stopped at a break point
The instruction processing unit 110, a break point list management unit 111 that holds information about set break points, and a correction point setting unit 116 that automatically sets break points at edited points such as changes, additions, and deletions. Hereinafter, changing the source code by an operator's operation such as change, addition, and deletion will be referred to as editing or correction.

The editor unit 13 edits the source code according to the editing operation from the operator. The source code editing unit 112, and the file name and line number of the portion edited in the source code editing process are the source of the file. It comprises a modified line list management unit 115 stored as a position on the code, a source code display unit 113 for displaying the read source code on a display or the like, and a source code file management unit 114 for holding the source code file.

Here, the source code display section 108 and the source code display section 113 of the editor section 13 and the debugger section 12 may be common. Command input section 10
2 is from the operator "edit file open command", "edit file save command", "edit command", "debug processing start command", "breakpoint setting command", "breakpoint cancel command", "program execution command" Also, commands such as "debug processing end command" are accepted. The command processing relating to the display / setting of data is not a particularly important part of the present invention, and therefore its explanation is omitted.

The command analysis unit 103 analyzes the command received by the command input unit 102, and instructs each component according to the analysis result to realize the function of each command. Below, first of all, "Edit File Open Command", which is the same command as the conventional technology,
The "edit file save command", "breakpoint setting command", "breakpoint cancel command" and "program execution command" will be described. Since these are conventional techniques, they will be briefly described by omitting the drawings. Next, "editing command", "debug processing start command" and "debug processing end command" which are the characteristic commands of the present invention will be described with reference to the drawings. <Edit File Open Command> Step 11: The command input unit 102 receives an edit file open command specifying a file name to be edited from the operator.

Step 12: Source code editing unit 112
Requests the source code file management unit 114 to read the source code of the specified file name. Step 13: The source code file management unit 114
The source code of the specified file name is read from the recording medium recording the source code file and passed to the source code editing unit 112.

Step 14: Source code editing unit 112
Requests the source code display unit 113 to display the read source code. Step 15: The source code display unit 113 displays the source code requested to be displayed on the display. <Edit File Save Command> Step 31: The command input unit 102 receives an edit file save command in which a file name to be saved is specified by the operator.

Step 32: Source code editing unit 112
Requests the source code file management unit 114 to save the source code of the specified file name. Step 33: The source code file management unit 114
The source code requested to be saved is written in the recording medium. <Breakpoint Setting Command> Step 51: The command input unit 102 receives a breakpoint setting command specifying a file name and a line number in which a breakpoint should be set. Specifically, this breakpoint setting command, with the source code displayed on the display,
When the operator places the mouse pointer on any line on the source code and clicks it, the command input unit 102
However, the breakpoint setting command is accepted by designating the line number of the clicked position and the file name of the source code being displayed as the line number and the file name.

Step 52: The loading unit 105 requests the breakpoint setting / cancelling unit 106 to set a breakpoint. Step 53: Break point setting / cancellation unit 106
From the debug info in the loaded executable,
Get the address for the breakpoint setting line.

Step 54: The break point setting / cancellation unit 106 causes the break point list management unit 111 to
Requests that the address where the breakpoint is set and the instruction at that address be registered in the breakpoint list. Here, the breakpoint list is composed of an address column for storing the address in the executable file corresponding to the breakpoint to be set and an instruction column for temporarily storing the instruction at the address in the address column. The groups and are arranged in ascending order of address.

Step 55: The breakpoint setting / cancelling unit 106 requests the source code display unit 108 to display the file for which the breakpoint is set. Step 56: The breakpoint list management unit 111
Addresses and instructions requested to be registered by the breakpoint setting / cancellation unit 106 are registered in the breakpoint list, and the instructions on the source code pointed to by these addresses are replaced with break instructions.

Step 57: Source code display section 108
Reads the file requested to be displayed from the source code file management unit 114 and displays it. And further,
The breakpoint display unit 109 is requested to display the breakpoint of the specified file. Step 58: The break point display unit 109 reads the break point list of the specified file from the break point list management unit 111 and displays the break points.

FIG. 2 shows an example of the break points displayed by the break point display section 109. As shown in the figure, "j = 5" in the source code before modification
00 "is corrected to" j = 10 ", and" printf ("i
=% D ", i);", "printf (" next_i
=% D ", i + 1);" and "printf (" con
“Tinue \ n”); ”was added, and as a result, the line“ j = 10 ”and“ print ”in the corrected source code
A black circle indicating a breakpoint is displayed at the left end of the line of f ("i =% d", i); ". <Breakpoint Release Command> Step 61: The command input unit 102 receives from the operator a breakpoint release command specifying the file name and line number of the breakpoint to be released. Specifically, when the operator puts the mouse point on the line where the breakpoint is set on the source code and clicks the command while the source code is displayed, the command input unit 102 clicks the breakpoint cancellation command. It accepts as an instruction to cancel the break point of the specified line.

Step 62: The loading unit 105 requests the breakpoint setting / cancelling unit 106 to cancel the breakpoint. Step 63: Break point setting / cancelling unit 106
From the debug info in the loaded executable,
Obtaining the address for the breakpoint cancellation line, requesting the breakpoint list management unit 111 to delete the address at the breakpoint cancellation location and the instruction within that address from the breakpoint list, and cancel the source code display unit 108. Request to view the file you created.

Step 64: The break point list management section 111 restores the original instruction and deletes the address and the instruction from the break point list. Step 65: The source code display unit 108 reads the specified file from the recording medium of the source code file management unit 114 and displays it. Then, the breakpoint display unit 109 is requested to display the breakpoint of the designated file.

Step 66: Break point display section 1
In step 09, the breakpoint list of the designated file is read from the breakpoint list management unit 111, and the breakpoints are displayed. <Program Execution Command> Step 71: The command input unit 102 receives a program execution command from the operator when executing the execution file in the debug device 10.

Step 72: The loading unit 105 requests the execution control unit 107 to execute the execution file. Step 73: The execution control unit 107 interprets and executes the instructions in the loaded execution file one by one, and breaks the instructions.
If there is an instruction, execution of the instruction is temporarily stopped and the break instruction processing unit 110 is requested to process the break instruction. Then, the source code display unit 108 is requested to display the source code of the place where the execution is stopped.

Step 74: break instruction processing unit 11
0 fetches the original instruction at the stopped address from the breakpoint list management unit 111, and passes the fetched instruction to the execution control unit 107 so as to be executed first in the next program execution. Step 75: The source code display unit 108 reads the specified file from the source code file management unit 114 and displays it, and then the breakpoint display unit 10
Reference numeral 9 reads the breakpoint list of the specified file, and displays a mark or the like indicating the breakpoint at the breakpoint position on the source code.

Next, before describing the characteristic commands of the present invention, the correction line list will be described. Figure 3
Shows an example of the correction line list. The modified line list is a table in which the line numbers of the editing operations performed by the operator on the source code are arranged in ascending order. The line number recorded in this table is the line number that sets the breakpoint. The corrected line list is arranged in the ascending order of line numbers, and the same line number is not registered doubly but is held for each source code file.

Next, "edit command", "debug processing start command" and "debug processing end command"
Will be described. <Edit Command> FIG. 4 is a flowchart showing a processing procedure when the command input unit 102 receives an edit command. This command is effective when the file is read and displayed by the edit file open command.

Step S301: Source code editor 1
12 determines whether or not the debug processing has ended. Step S302: If the result of determination in step S301 is that the debug processing has not ended, the source code editing unit 112 sends a “debug processing end command” to the command input unit 102, and as a result, the debug processing ends. .

Step S303: It is determined whether the type of edit made by the edit command is deletion of line feed code, addition of line feed code, or other editing process.
Deleting a line feed code is an edit that only deletes the line feed code or an edit that includes the deletion of a line feed code.Adding a line feed code is an edit that only adds a line feed code or an edit that includes the addition of a line feed code. The edit process is an edit that does not involve deleting or adding a line feed code.

Step S304: If the type of editing is other editing processing, the row number of the row subjected to the other editing processing is registered in the corrected row list. Step S305: When the type of editing is deletion of line feed code, the line number of the line feed deletion is registered in the correction line list, and 1 is subtracted from the line number larger than the line number of the line feed deletion line in the correction line list. .

Step S306: If the type of editing is adding a line feed code and the position of addition is at the beginning of the line,
Add 1 to the line number that is greater than or equal to the line number of the new line added line in the corrected line list. Step S307: When the type of editing is addition of a line feed code and the position of the addition is at the end of the line, 1 is added to a number larger than the line number of the line feed added line in the corrected line list.

Step S308: If the type of editing is the addition of a line feed code and the position of the addition is a line feed code in the line, that is, at a position that is neither the beginning nor the end of the line, the line feed in the correction line list 1 is added to the line number larger than the line number of the added line, and the line number of the line feed added line and the line number of the line feed added line + 1 are registered in the corrected line list. Step S309: The source code editing unit 112 performs an edit process on the source code read and displayed by the edit file open command, and requests the source code display unit 108 to update the display.

Step S310: Source code display section 1
08 updates the display by reflecting the edited contents. In this way, the source code editing unit 112 manages the position on the source code of the edited part by registering the line number of the edited part in the correction line list.

In addition, in the registration of the line numbers in steps S304, S305 and S308, if the same line number to be newly registered has already been registered in the corrected line list, do not register. Prevent double registration. More specifically, it is determined whether or not the line number to be registered is already registered in the corrected line list, and if it is not registered yet, it is registered, and if it is already registered, it is not registered.

In the present embodiment, the editing process is constantly monitored and the correction line list is updated every time there is an editing process. However, the present invention is not limited to this, and the original source code before the editing process is changed. Alternatively, the modified line list may be created by comparing the edited source code with the original source code after the editing process is completed. <Debug Processing Start Command> FIG. 5 is a flowchart showing a processing procedure when the command input unit 102 receives a debug processing start command. Although omitted in FIG. 5, the processes of the following steps S41 to S43 are performed prior to the processes of step S400 and subsequent steps.

Step S41: If there is a source code that is being edited, the loading section 105 sends an edit file save command to the source code. Then, the execution file management unit 104 is requested to read the latest execution file. Step S42: The execution file management unit 104 checks the date and time of the source code of the source code file management unit 114 and determines whether or not there is a source code file newer than the execution file.

Step S43: If the result of determination in step S42 is that there is a new source code file, the source code file is compiled, the latest execution file is created, and the latest execution file is loaded into the loading unit 105. hand over. As a result of the determination in step S42, if there is no new source code file,
The execution file management unit 104 transfers the latest execution file held therein to the loading unit 105.

Step S400: The loading unit 105 loads the latest executable file, and the correction location setting unit 116
Request to set a breakpoint on the line indicated by the modified line list. Step S401: The correction location setting unit 116 determines whether the correction line list management unit 115 has a correction line list that has not been read yet.

Step S402: As a result of the judgment, if there is a correction line list which has not been read yet, it is read. Step S403: The correction location setting unit 116 determines whether or not there is one or more correction line numbers in the read correction line list. Step S404: If the result of determination is that there is one or more correction line numbers, the correction line number at the beginning of the read correction line list is taken out as the target line, and a breakpoint setting command for the target line is executed. Send and set a breakpoint on the target line.

Step S405: Subsequently, the correction location setting unit 116 looks at the correction line list in order from the beginning, and determines whether there is a correction line number that has not been taken out yet. Step S406: If the result of determination is that there is a corrected line number that has not been taken out, the corrected line number next to the target line is taken out and set as the target line. Step S407: A break point setting command is sent to the target line to set a break point on the target line.

Step S408: When the breakpoints have been set for all the corrected lines, the corrected line list management unit 115 discards the corrected line list. As described above, the correction point setting unit 116 causes the break point setting / cancelling unit 106 to set a break point by sending a break point setting command designating a correction line listed in the correction line list.

Although the corrected line list is discarded, the corrected line list is deleted by deleting an unnecessary portion immediately before creating the corrected line list from the breakpoint list in the process of the debug process end command. It may be an alternative to discarding. <Debug Processing End Command> FIG. 6 is a flowchart showing a processing procedure when the command input unit 102 receives a debug processing end command.

Step S501: The loading section 105 requests the modified row list management section 115 to create a modified row list from the breakpoint list managed by the breakpoint list management section 111. Next, the corrected line list management unit 11
5 converts the address of the breakpoint list of the breakpoint list management unit 111 into a file name and a line number using the debug information of the loaded execution file,
Create a list of modified lines for each file.

Step S502: The load unit 105 issues a request to the breakpoint list management unit 111 to discard the breakpoint list, and the breakpoint list management unit 111 discards the breakpoint list. Step S503: The loading unit 105 unloads the execution file. With the configuration described above, the programmer does not need to set a breakpoint at the correction point by himself, and the troublesomeness at the time of setting a breakpoint is released, and the debugging efficiency is improved. In addition, when the programmer makes the settings, it may not be possible to set all the correction points without fail because the programmer forgets to do the settings. However, if the debug device 10 makes the settings, all the correction points will not be lost. You can test the behavior and so on. <Second Embodiment> FIG. 7 is a block diagram of a debug device according to a second embodiment.

In the figure, the debug device 20 includes a division / optimization unit 617 in addition to the configuration of the debug device 10 of FIG. 1 in the first embodiment. Hereinafter, description of the same points as those of the first embodiment will be omitted, and different points will be mainly described. FIG. 9 is a flowchart showing a processing procedure when the command input unit 102 receives a debug processing start command.

Although the process before step S800 is not shown in the figure, it is the same as step S41 to step S43 described in FIG. 5, and steps S800 to S804 and step S81.
The process of No. 2 is also the same as steps S400 to S404 and step S408 of FIG. 5, and therefore its explanation is omitted, and hereinafter, it will be explained from step S805.

Step S805: Division / optimization unit 617
Performs a control transfer preceding list creation process. Details of this processing will be described later with reference to FIG. Here, the control transition preceding list will be described. FIG. 8 shows an example of a control transition precedence list created and used by the debug device 20 according to the second embodiment.

The control transfer preceding refers to a line that may be executed subsequent to the execution of a line other than the line immediately above in the execution order of each line in the source code. For example, a line including a branch destination instruction of a branch instruction is a control transfer precedent. In the line order from the beginning of the source code, a block from one control transition preceding to the next control transition preceding is called a control block. That is, the control transition preceding list stores what line on the source code the first line of each control block forming the source code is, and thereby indicates the range of each control block.

The control transition precedence list of FIG. 8 is composed of a row number column for storing a line number and a control transition precedence flag indicating whether or not the row of the row number is the control transition precedence. The control transition preceding flag is set to 1 if the line of the line number is the control transition preceding, and is set to 0 otherwise. The first line of the source code always precedes the control transfer. This control transfer preceding list is created for each source file.

Step S806: Next, the correction location setting unit 116 looks at the correction line list in order from the beginning and determines whether there is a correction line number that has not been taken out yet. Step S807: If the result of determination is that there is a correction line number that has not been taken out, the correction line number next to the target line is taken out and set as the next target line. Step S808: In the control transition precedence list, it is determined whether or not the control transition precedence flag of the next target row is 1.

Step S809: If it is determined in step S808 that it is not 1, the division / optimization unit 617 determines whether the line number of the next target line matches the line number obtained by adding 1 to the target line. To determine. That is, in this determination, it is determined whether the target line and the next target line are continuous. Step S810: When the control transition preceding flag of the next target line is 1 in the determination of step S808, and when the line number of the next target line and the target line are 1 in step S809.
If the line number added with does not match, the division / optimization unit 6
17 sends a breakpoint setting command to set a breakpoint on the next target line.

Step S811: The next target line is set as the target line, and the process returns to step S806. In this way,
The optimization unit 617 determines that the corrected line is the control transition precedent,
If the modified line does not have a line number that follows the line number of the immediately preceding modified line, a breakpoint is set for the modified line, the modified line is not the control transition preceding, and
If the modified line has a line number that follows the line number of the immediately preceding modified line, no breakpoint is set for the modified line.

The dividing / optimizing unit 617 may have a simpler structure as follows. That is, the division / optimization unit 617 breaks points among the modified lines listed in the modified line list that are listed as the control migration precedent in the control migration preceding list, that is, the lines in which the control migration preceding flag is 1. May be configured to be set. Further, the division / optimization unit 617 may be configured not to set a break point when a line immediately above the corrected line among the corrected lines listed in the corrected line list is also the corrected line. Good.

Further, the division / optimization unit 617 may be configured to set a break point only to the first correction line among the correction lines in the control block for each control block indicated by the control transition preceding list. Further, for each control block, the division / optimization unit 617 sets a break point in the first row of the control block when a modified row exists in the control block, and sets a breakpoint in the modified row other than the first row. The configuration may be omitted.
In addition to this configuration, when a plurality of modified lines are consecutive in the control block, the break point may be set only in the first modified line.

FIG. 10 is a flow chart showing a detailed processing procedure of the control transition preceding list creation processing of step S805. Step S901: The division / optimization unit 617 reads the source code of the read corrected line list. Step S902: Initialize various variables for later word analysis processing. That is, the current line is set to 0, the control transition leading flag is set to 1, the next sentence start flag is set to 0, the middle flag is set to 0, and the parenthesis count is set to -1.

Step S903: It is determined whether or not there is a current row + 1 row. Step S904: If the result of determination in step S903 is that there is a current row + 1 row, that row is extracted and set as the current row. Step S905: Divide the current line into delimiters and divide into words. Here, the term delimiter refers to a predetermined character string included in the source code. This predetermined character string is a space, a control character, // ... line end, /*...*/, ".
.. ", (,), {,} ,; and: The part of" ... "in this predetermined character string is an arbitrary character string. Among the delimiters, (,), {,},;,: are particularly referred to as word delimiters. A character string consisting of one or more characters separated by a delimiter and a word delimiter are collectively referred to as a word. An example in which a program and a program are divided into words is shown in FIGS. 19 and 20.

Step S906: Words are searched in order from the beginning of the current line. Step S907: It is determined whether a word has been searched. Step S908: If the result of determination in step S907 is that a word is found, word analysis processing is performed. Details of this processing will be described later with reference to FIG. Step S909: Search the next word from the current line and return to step S907.

Step S910: If the result of determination in step S907 is that no word is found, the control transition preceding flag value is assigned to the control transition preceding flag column corresponding to the line number of the current line in the control transition preceding list. Thereafter, the control transition leading flag is set to 0, and the process returns to step S903. FIG. 11A is a flowchart showing a detailed processing procedure of the word analysis processing in step S908. In this word analysis processing, words are classified into classifications 1 to 6 and “others”, and different processing is performed according to the classification. FIG. 11 (b)
Shows the contents of categories 1 to 6.

Step S1001: The parenthesis count is −
It is determined whether it is greater than 1. Step S1008: If the result of determination in step S1001 is that the parenthesis count is not greater than -1, and the word belongs to classification 1, that is, the word is ":" or "}".
If it is, 1 is set to the next sentence head flag. Step S1009: If the result of determination in step S1001 is that the parenthesis count is not greater than −1 and the word belongs to classification 2, the parenthesis count is set to 0 and the middle flag is set to 1.

Step S1010: Step S1001
As a result of the judgment, the parenthesis count is not greater than -1,
If the word belongs to the category 3, 1 is set to the next sentence head flag and 1 is set to the middle flag. Step S1011: If the result of determination in step S1001 is that the parenthesis count is not greater than −1 and the word belongs to classification 5, the middle flag is set to 0.

Step S1012: Step S1001
As a result of the judgment, the parenthesis count is not greater than -1,
If the word belongs to classification 4, it is determined whether the next sentence head flag is 1. Step S1013: If the result of determination in step S1012 is that the next sentence start flag is 1, the control transition preceding flag is set to 1 and the next sentence start flag is set to 0.

Step S1014: Subsequently, it is determined whether or not the medium flag is 1. Step S1015: If the result of determination in step S1014 is that the medium flag is 1, the next sentence start flag is 1
Is set, and 0 is set to the middle flag. If the result of determination in step S1001 is that the parenthesis count is not greater than -1, and the word does not belong to any classification, nothing is done.

Step S1002: Step S1001
When the parenthesis count is larger than -1 as a result of the determination of, it is determined whether the word belongs to the classification 6. Step S1003: If the result of the determination in step S1002 is that the word belongs to classification 6, it is further determined whether or not the word is “(”. Step S1004: As a result of the determination in step S1003, the word is “ If it is (), the value of the parenthesis count is incremented by 1.

Step S1005: Step S1003
If the word is not “(” as a result of the determination, the value of the parenthesis count is decremented by 1. Step S1006: It is determined whether the parenthesis count is 0. Step S1007: The result of the determination in step S1006 is the parentheses If the count is 0, the parenthesis count is set to -1.

Here, the classifications 1 to 6 are classifications when the source code is described in C language,
Class 1 if written in Java (registered trademark)
":" And "}" in addition to "catch" and "fi"
"nally" may be added as a keyword for classification. In the flowcharts of FIGS. 10 and 11, the words are analyzed in order from the beginning of the source code, and the line found by the following methods 1 and 2 is set as the control transfer precedence. 1. The words are sequentially searched from the beginning of the source code, and when a word of category 1 ":,}" or category 3 "else" is found, the line with the word of category 4 ";" that appears for the first time is set as the control transition precedent. . 2. Looking at the words in order from the beginning of the source code, and when the middle flag is 1, when a word of class 4 ";" is found, the line with the word of class 4 ";" that appears for the first time as the control transition precedent. To do.

Here, the case where the middle flag is 1 means that the words are sequentially searched from the beginning of the source code, and the classification 2 "if, for, while" and the classification 3 "els" are performed.
"e" is found. However, classification 2 "i
Words in the conditional expression "f, for, while" are ignored. In the above methods 1 and 2, if, for, while
If there is {or} after e, else but not after e, else, the line of the classification 4 ";" that is found first after} is regarded as the control transition preceding, so an extra control block can be created. The algorithm has the advantage of being able to find the control transition precedent, and guarantees that there is no failure that the control transition precedent is not regarded as the control transition precedent. <Third Embodiment> FIG. 12 is a block diagram of a debug device according to a third embodiment.

In the figure, the debug device 30 includes a bug form management unit 1118 in addition to the configuration of the debug device 20 of FIG. 7 in the second embodiment. Hereinafter, description of the same points as those of the second embodiment will be omitted, and different points will be mainly described. FIG. 13 shows an example of a bug vote list. The bug form list is composed of a plurality of bug forms, and each bug form is composed of a bug form number, which is a number uniquely indicating the bug form, a comment, and the number of passages.

The comment is composed of the file name of the source code having the breakpoint setting line, the setting line number, and the comment input by the operator for each of the one or more breakpoint setting lines. The comment of each line is input by the operator about the correction content and the like every time the breakpoint is set. In addition, information such as a modification date and time may be automatically described in the comment of each line.

The number of passages corresponds to each break point setting line in the comment field, and indicates the number of times the command statement on the break point setting line is executed. FIG. 14 is a flowchart showing a processing procedure when the command input unit 102 receives a debug processing end command. Step S1301: The loading unit 105 requests the modified row list management unit 115 to create a modified row list from the breakpoint list managed by the breakpoint list management unit 111. Next, the modified line list management unit 115 converts the address of the breakpoint list of the breakpoint list management unit 111 into the file name and line number using the debug information of the loaded execution file, and the modified line for each file. Create a list.

Step S1302: The loading section 105
The breakpoint list management unit 111 issues a request to discard the breakpoint list, and the breakpoint list management unit 111 discards the breakpoint list. Step S1303: 0 is assigned to the breakpoint setting address of the bug vote list.

Step S1304: The loading section 105
Unload the executable file. FIG. 15 is a flowchart showing a processing procedure when the command input unit 102 receives a debug processing start command. In the figure, the process before step S801, step S8
Since the subsequent processing in the case of “Yes” in 01 and step S812 are the same as those in the flowchart of FIG. 9, illustration thereof is partially omitted. Since these parts have the same processing procedure as in FIG. 9, description thereof will be omitted.
Hereinafter, step S1401 and step S1402 which are different from FIG. 9 will be described.

Step S1401: Excluding the last bug vote from the bug vote list, it is determined whether or not there is a bug vote whose breakpoint setting address is 0. Step S1402: As a result of the determination, if there is a bug vote in which the breakpoint setting address is 0, the bug vote closing process shown in FIG. 18 is performed. FIG. 16 is a flowchart showing a processing procedure when the command input unit 102 receives a breakpoint setting command.

Step S1501: Command input unit 10
When 2 receives the breakpoint setting command, the loading unit 105 causes the breakpoint setting / cancelling unit 106 to
To set a breakpoint, the breakpoint setting / cancellation unit 106 obtains the address for the breakpoint setting line from the debug information in the loaded execution file.

Step S1502: It is judged whether the bug vote for which the breakpoint setting address is to be registered is new or has been registered in the bug vote list. Step S1503: If the result of determination in step S1502 is that the bug vote is new, the breakpoint setting address is written in the bug vote at the end of the bug vote list, and the breakpoint setting address is addressed at the beginning of the comment. Describe the file name and line number.

Step S1504: The comment input by the operator is described following the file name and line number. Step S1505: A bug form in which only the bug form number is described is created and registered at the end of the bug form list. A serial number is assigned to the bug vote number. Step S1506: If the result of determination in step S1502 is that the bug form is already registered in the bug form list,
Search for the desired bug form from the list of bug forms.

Step S1507: The breakpoint setting address is written in the bug form, and the file name and line number corresponding to the breakpoint setting address are described at the beginning of the comment. Step S1508: Describe the comment input by the operator. Step S1509: It is determined whether or not there is another bug vote for which the breakpoint setting address should be registered.

Step S1510: The breakpoint list management unit 111 registers the address and the instruction in the breakpoint list, and replaces the instruction in the address with the break instruction. Step S1511: The source code display unit 108 reads the file requested to be displayed from the source code file management unit 114 and displays it. Then, it further requests the breakpoint display unit 109 to display the breakpoints of the specified file. Then, the breakpoint display unit 109 displays the breakpoint list management unit 1
The breakpoint information of the file designated from 11 is read and the breakpoint is displayed.

FIG. 17 is a flowchart showing a processing procedure when the command input unit 102 receives a breakpoint cancellation command. Step S1601: The loading unit 105 requests the breakpoint setting / cancelling unit 106 to cancel the breakpoint. Upon receiving this request, the breakpoint setting / cancellation unit 106 obtains the address for the breakpoint cancellation line from the debug information in the loaded execution file. Then, the bug vote management unit 1118 is requested to delete the breakpoint to be canceled from the bug vote. Then, the breakpoint list management unit 111 is requested to delete the address of the location where the breakpoint is to be released and the instruction within the address from the breakpoint list, and the source code display unit 108 is to display the released file. Request.

Step S1602: Bug form managing unit 111
8 targets the first bug vote in the bug vote list. Step S1603: Subsequently, the bug vote management unit 1118
Searches for breakpoint release addresses in order from the list of breakpoint setting addresses for the target bug vote.

Step S1604: Next, step S1
As a result of the search in 603, the bug vote management unit 1118 determines whether or not a bug vote having a breakpoint cancellation address has been found. Step S1605: When a bug vote having a breakpoint cancellation address is found as a result of the determination in step S1604, the bug vote management unit 1118 targets the bug vote.

Step S1606: Bug form management unit 111
Step 8 deletes the break point cancellation address from the break point setting address list of the target bug vote. Step S1607: Subsequently, the bug vote management unit 1118
Determines whether there is nothing in the breakpoint setting line list of the target bug vote. Step S1608: If the result of the determination in step S1607 is that there is, it is further determined whether or not there is a bug vote next to the target bug vote from the bug vote list.

Step S1609: Step S1608
If it is determined that there is a bug vote, the next bug vote is targeted. Step S1610: If the result of determination in step S1607 is that there is nothing in the breakpoint setting line list of the target bug slip, the bug slip close processing shown in FIG. 18 is performed.

Step S1611: The breakpoint list management section 111 restores the original instruction and then deletes the address and the instruction from the breakpoint list. Step S1612: The source code display unit 108 stores the designated file in the source code file management unit 114.
Read from and display. Then, the breakpoint display unit 109 is requested to display the breakpoint of the specified file. The break point display section 109 is
The breakpoint information of the specified file is read from the breakpoint list management unit 111 and the breakpoints are displayed.

FIG. 18 is a flow chart showing the detailed processing procedure of the bug slip close processing. Step S1701: The bug form management unit 1118 adds the test result and closes the bug form. Step S1702: Subsequently, the bug form management unit 1118
Delete the closed bug vote from the bug vote list.

With the above configuration, the debug device 30
Since the bug vote is managed for each breakpoint, the programmer can write the comment of the correction contents efficiently.

[0099]

The breakpoint setting device of the present invention is
Loading means for loading an execution format program generated based on the source program, and storage means for storing information indicating a correspondence relationship between each element configuring the source program and each location configuring the execution format program And when the source program is edited, and when the edited content is a specific one, it indicates to which of the elements configuring the source program the specific edit is made. An acquisition unit that acquires and stores the position information, and a setting unit that sets a breakpoint at a location in the loaded executable program corresponding to an element indicated by the position information acquired by the acquisition unit are provided.

According to this structure, the breakpoint setting device manages the edited portion on the source program edited by the operator's editing operation to grasp the position of the edited portion on the source program and set the position to the position. Since the breakpoint is set, it is not necessary for the operator to instruct the setting of the breakpoint and the position of the editing point.

Further, each element is each line constituting the source program, and the information stored in the storage means indicates a correspondence between a line number for identifying each line and each location. The acquisition means may be configured to acquire and store, as the position information, a line number of a line in the source program in which a specific edit has been made.

Further, the specific edit includes deletion of a line feed code, and the breakpoint setting device is further configured so that when the source program is edited,
When the edit content of the edit location is the deletion of the line feed code, the line number of the edit location is stored, and the line number of the line related to the edit is stored among the line numbers already acquired and stored by the acquisition unit. It is also possible to provide an updating unit that rewrites each line number having a large number with a line number having a smaller value by one.

The breakpoint setting device is
Further, in the case where the source program is edited, when the edited content of the edited portion is addition of a line feed code to the beginning of the line, the same line number as the edited portion among the line numbers already acquired and stored by the acquisition means. An updating unit may be provided for rewriting the line number and the line number having a larger value than the line number of the edited part into a line number having a value larger by one.

Also, the break point setting device is
Further, in the case where the source program is edited, if the edited content of the edited part is addition of a line feed code to the end of the line, the line number from the edited part among the line numbers already acquired and stored by the acquisition means. Also, an updating unit for rewriting a row number having a large value into a value having a larger value may be provided.

Further, the specific edit includes addition of a line feed code in the line, and the breakpoint setting device further edits the edit content of the edit location when the source program is edited. When a line feed code is added to a line, each line number having a value larger than the line number of the editing location among the line numbers already acquired and stored by the acquisition means is written as a value one larger. Alternatively, an updating unit may be provided that newly stores the line number of the edit location and the line number whose value is one greater than the line number of the edit location.

Further, the obtaining means, when the source program is edited, a determining means for determining whether or not the editing content of the editing location is editing for a character string other than a line feed code, and the determining means. If the determination is affirmatively determined by, an updating unit that newly stores the line number of the edited location of the edited location may be provided. According to this configuration, the breakpoint setting device determines whether the edit includes deletion or addition of a line feed code, and if the line feed code is added, whether the addition position is at the beginning of the line, in the line, or at the end of the line. Since the editing position on the source program that moves accordingly can be grasped, the break point can always be set at an accurate position without the setting instruction and the designation of the setting position by the operator.

Further, the acquisition means further stores line range information indicating a range of each control block forming the source program from a position on the source program to a position on the source program by the line number. The means may set a breakpoint at a corresponding position on the executable program corresponding to the top line number of each control block indicated by the line range information.

According to this structure, the break point can be set for each control block, for the first correction row in the control block. In addition, the setting means, among the line numbers stored by the acquisition means,
The break point of the corresponding portion may not be set for the line number after the two line numbers that are continuous before and after.

According to this structure, when the edit position exists in both two consecutive lines on the source program, the break point setting to the edit position of the subsequent line is omitted and the break point is set only to the edit position of the previous line. Can be set. Further, the break point setting device creates a bug vote in which information on an edit location corresponding to the break point input by the user for each break point set by the setting means is created, and the bug note is set by the user. It may be presented to the user via an interface.

According to this structure, the breakpoint setting device manages the edited portion on the source program edited by the operator's editing operation to grasp the position of the edited portion on the source program, and set the position to the position. Since it is possible to set a breakpoint and create a bug form, the burden on the operator of creating a bug form is reduced.

[Brief description of drawings]

FIG. 1 is a block diagram of a debug device according to a first embodiment.

FIG. 2 shows an example of break points displayed by a break point display unit 109.

FIG. 3 shows an example of a corrected row list.

FIG. 4 is a flowchart showing a processing procedure when the command input unit 102 receives an edit command.

FIG. 5 is a flowchart showing a processing procedure when the command input unit 102 receives a debug processing start command.

FIG. 6 is a flowchart showing a processing procedure when the command input unit 102 receives a debug processing end command.

FIG. 7 is a block diagram of a debug device according to a second embodiment.

FIG. 8 shows an example of a control transition preceding list created and used by the debug device 20 according to the second embodiment.

FIG. 9 is a flowchart showing a processing procedure when the command input unit 102 receives a debug processing start command.

FIG. 10 is a flowchart showing a detailed processing procedure of a control transition preceding list creation processing of step S805.

FIG. 11A is a flowchart showing a detailed processing procedure of word analysis processing in step S908. (B)
Indicates the contents of classifications 1 to 6.

FIG. 12 is a block diagram of a debug device according to a third embodiment.

FIG. 13 shows an example of a bug vote list.

FIG. 14 is a flowchart showing a processing procedure when the command input unit receives a debug processing end command.

FIG. 15 is a flowchart showing a processing procedure when the command input unit 102 receives a debug processing start command.

16 is a flowchart showing a processing procedure when the command input unit 102 receives a breakpoint setting command. FIG.

FIG. 17 is a flowchart showing a processing procedure when the command input unit 102 receives a breakpoint cancellation command.

FIG. 18 is a flowchart showing a detailed processing procedure of a bug form closing process.

FIG. 19 shows an example of a program

FIG. 20 shows an example in which the program of FIG. 19 is divided into words.

[Explanation of symbols]

10 Debugging device 11 Makeup Department 12 Debugger section 13 Editor 20 Debugging device 30 Debugging device 102 Command input section 103 Command parser 104 Executable file manager 105 Road section 106 Release unit 107 execution control unit 108 Source code display 109 Break point display 110 Command processing unit 111 Breakpoint List Management Department 112 Source code editor 113 Source code display 114 Source Code File Management Department 115 Modified row list management section 116 Correction point setting section 617 Optimization unit 1118 Bug form management department

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Takuji Kawamoto             2-6-1, Sakae, Naka-ku, Nagoya-shi, Aichi             Kawa Building Annex 5th floor Matsushita Electric Information Co., Ltd.             Stem Nagoya Institute F term (reference) 5B042 HH01 HH25 LA02 MA10 MC13                       NN04 NN06                 5B076 EC01 EC02 EC04

Claims (15)

[Claims] 1. A load means for loading an execution format program generated based on a source program, and information storing a correspondence relationship between each element configuring the source program and each location configuring the execution format program. When the source program is edited, and the edited contents are specific, the specific edit is performed on any of the elements constituting the source program. Acquiring means for acquiring and storing position information indicating whether the position information has been processed, and setting means for setting a break point at a position in the loaded executable program corresponding to an element indicated by the position information acquired by the acquiring means. And a break point setting device. 2. Each of the elements is a line constituting the source program, and the information stored in the storage means indicates a correspondence relationship between a line number for identifying each of the lines and each of the locations. 2. The break point setting device according to claim 1, wherein the acquisition unit acquires and stores, as the position information, a line number of a line in the source program in which a specific edit has been performed. 3. The specific edit includes deletion of a line feed code, and the breakpoint setting device further includes: when the source program is edited, edit contents of the edited portion include deletion of a line feed code. , The line number of the edited part is stored, and the line number having a value larger than the line number of the line related to the editing among the line numbers already acquired and stored by the acquisition means has a value of 1
The break point setting device according to claim 2, further comprising an updating unit that rewrites the line number to a smaller row number. 4. The break point setting device further stores, when the source program is edited, when the edited content of the edited portion is addition of a line feed code to the beginning of a line, the breakpoint is already acquired by the acquisition means and stored. The line number that is the same as the edit location and the line number that is larger than the line number of the edit location have the value 1
The break point setting device according to claim 2, further comprising an updating unit that rewrites the line number to a larger line number. 5. The breakpoint setting device further includes, when the source program is edited, when the edited content of the edited location is addition of a line feed code to the end of a line, the breakpoint is already acquired by the acquisition means. 3. The breakpoint setting device according to claim 2, further comprising an updating unit that rewrites a line number having a larger value than the edited location among the stored line numbers to a value having a larger value by one. 6. The specific edit includes addition of a line feed code in a line, and the breakpoint setting device further includes: when the source program is edited, the edit content of the edit location. When a line feed code is added to a line, each line number having a value larger than the line number of the editing location among the line numbers already acquired and stored by the acquisition means is written as a value one larger. 3. The breakpoint setting device according to claim 2, further comprising update means for newly storing a line number of the edited location and a line number having a value one greater than the line number of the edited location. 7. The determining means, when the source program is edited, determining means for determining whether or not the editing content of the editing location is editing for a character string other than a line feed code, and the determining means. 3. The break point setting device according to claim 2, further comprising: an updating unit that newly stores the line number of the edited location of the edited location when the determination is positive. 8. The acquisition means further stores line range information indicating a range of each control block constituting the source program from a position on the source program to a position on the source program by line numbers. 3. The break point setting device according to claim 2, wherein the means sets a break point at a corresponding position on the executable program corresponding to the top line number of each control block indicated by the line range information. 9. The setting unit does not set a break point at a corresponding position for a line number subsequent to two line numbers that are consecutive before and after the line number stored in the acquisition unit. The break point setting device according to claim 2, wherein: 10. The break point setting device creates a bug slip in which information on an edit location corresponding to the break point input by the user is associated with each break point set by the setting means, and the bug The breakpoint setting device according to claim 1, wherein the vote is presented to the user via a user interface. 11. The breakpoint setting device acquires, from the debugger, the number of times the editorial portion has been decoded and executed by the debugger in creating the bug form, and presents the number of times in the information on the edited portion. The break point setting device according to claim 10, wherein 12. The acquisition unit according to claim 1, wherein, when the position information corresponding to the specific edit is already acquired and stored, the acquisition unit suppresses storing the position information. Break point setting device. 13. The acquisition means further stores line range information indicating a range of each control block constituting the source program from a position on the source program to a position on the source program, wherein the setting is performed. The means sets, for each control block, a break point at the beginning of each line in the control block that has been subjected to the specific edit, and prevents a break point from being set at other lines. The break point setting device according to claim 2. 14. A load step of loading an execution format program generated based on a source program, and information indicating a correspondence relationship between each element configuring the source program and each location configuring the execution format program in a memory. And a step of storing the source program, and when the edit content is a specific one, the specific edit is performed for any one of the elements constituting the source program. An acquisition step of acquiring and storing in memory the position information indicating whether the position information has been processed, and a setting for setting a breakpoint at a location in the loaded executable program corresponding to an element indicated by the position information acquired by the acquisition step. A breakpoint setting method comprising: 15. A program to be executed by a computer, the program comprising: a loading step of loading an execution format program generated based on a source program into the computer; elements constituting the source program; and the execution format. A storage step of storing information indicating a correspondence relationship with each part constituting the program in a memory, and a case where the source program is edited, and when the edited content is specific, the identification An acquisition step of acquiring and storing in memory the position information indicating which of the elements making up the source program has been edited, and the position acquired by the acquisition step in the loaded executable program. Set a breakpoint at the location corresponding to the element pointed to by the information Breakpoint setting program for causing running set and steps that, a.