JP6369177B2 - Development support program, development support method, and development support apparatus - Google Patents

Description

  The present invention relates to a development support program, a development support method, and a development support apparatus.

  The development support program analyzes the coded source code, detects problem areas that are suspected of having problems from various viewpoints, and outputs both the detected problem areas and problem indications that describe the suspected problems. . Specifically, the development support program is executed by a computer, and the source code is parsed without executing the source code to be analyzed, and the grammatical error, variable definition error, and program acquisition are acquired. Detect problem areas that are suspected of problems such as lack of memory area release processing, logical mistakes, etc., and problem indication statements that describe the line numbers of all problem areas and the problems that are the reason for the detection The problem part output data which lists together is generated.

  The development support program is described in the following patent document, for example.

  It is useful for the development support program to output all problem locations and problem indications at the initial stage of source code development. This is because the program developer can check all possible parts of the source code and make the necessary corrections. In this case, the program developer examines all problem areas that are suspected of problems with reference to the problem indication sentence, and makes corrections if necessary. Therefore, some problems may not be found as a result of checking, and no correction may be made.

  However, at the stage of revising the original or previous source code by changing or adding it, the problems remaining in the previous source code have already been considered. Therefore, it is necessary to exclude the problem part that has remained from before from the output data of the problem part for the revised source code. By excluding it, the check process based on the problem location list can be shortened.

  A block of source code that describes a series of processes including the problem part output for the previous source code, for example, a subroutine, a method, a function (hereinafter referred to as a subroutine), and an output for the revised source code If the subroutine containing the problem part is the same, there is a high possibility that the problem part is duplicated. Therefore, the development support program considers the problem location for the same location if the subroutine containing the problem location detected in the revised source code matches the problem location subroutine detected in the previous source code. Is excluded from the problem part output data of the revised source code.

JP 2004-126866 A JP 05-94343 A

  However, in order to detect a duplicate problem location based on whether or not the source code of the subroutine containing the problem location matches, it is necessary to retain the previous source code, which increases the amount of assets to be managed. In addition, the processing time for determining whether or not the subroutine including the problem part matches is long, and the analysis throughput deteriorates. In addition, since various changes are made to the revised source code, only minor changes that do not affect the problem part of the previous source code are made if it is judged simply by whether or not the subroutine matches. Even if they are not, the subroutines do not match, and it is not possible to exclude the duplicated problems.

  Therefore, the purpose of the first aspect of the embodiment is to provide a development support program, a development support method, and a development support that excludes a part of a revised source code from a part that overlaps with a part of the previous source code and outputs it. To provide an apparatus.

In the first aspect of the present embodiment,
Analyzing the second source code generated by updating the first source code to detect the second problem portion;
Generating second description specifying information for specifying a description from the top of a subroutine in which the second problem part is described to at least the second problem part;
The second description specifying information corresponding to the second problem location detected by analyzing the second source code corresponds to the first problem location detected by analyzing the first source code. The second problem location is excluded from the output target as the problem location of the second source code when the first description specifying information matches.
A computer-readable development support program that causes a computer to execute processing.

  According to the first aspect, a part that overlaps with a problem part of the previous source code is excluded from the problem part of the revised source code and output.

It is a figure which shows the structure of the development assistance apparatus which performs the development assistance program of this Embodiment. It is a figure which shows the 1st source code, the 1st problem part output data example produced | generated by analyzing it, the 2nd source code, and the 2nd problem part output data example produced | generated by analyzing it. . It is a flowchart figure which shows the process of the development assistance using the development assistance program in this Embodiment. It is a flowchart figure of the process of process S4, S5 of the development assistance program in this Embodiment. It is a figure explaining process S44 of FIG. It is a figure explaining the method to detect the subroutine containing a problem location in process S44. It is a figure which shows the 1st, 2nd source code in this Embodiment, and the 1st example of the 1st, 2nd problem location output data. It is a figure which shows the 2nd example of the 1st, 2nd source code in this Embodiment, and its 1st, 2nd problem location output data. It is another figure explaining process S44 of FIG. It is a figure which shows the 3rd example of the 1st, 2nd source code in this Embodiment, and its 1st, 2nd problem location output data. It is a figure which shows the 4th example of the 1st, 2nd source code in this Embodiment, and its 1st, 2nd problem location output data. It is a figure which shows the 5th example of the 1st, 2nd source code in this Embodiment, and its 1st, 2nd problem location output data. It is a figure which shows the 6th example of the 1st, 2nd source code in this Embodiment, and its 1st, 2nd problem location output data. It is a 2nd flowchart figure of the process of process S4, S5 of the development assistance program in this Embodiment. It is a figure which shows the 7th example of the 1st, 2nd source code in this Embodiment, and its 1st, 2nd problem location output data.

  FIG. 1 is a diagram showing a configuration of a development support apparatus that executes the development support program of the present embodiment. The development support apparatus includes a development support program 20, a CPU (Central Processing Unit) 10 that executes the development support program, a RAM 12 that temporarily stores the development support program and data, and an input / output device 14. The development support program 20 is stored in a mass storage device such as a hard disk. Further, the development support apparatus stores the problem source output data 22 of the first source code generated by analyzing the first source code and the second source code 24 to be analyzed in the mass storage device. ing. Then, the development support apparatus causes the CPU 10 to execute the development support program, analyzes the second source code 24, generates problem part output data 26 of the second source code, and stores it in the mass storage device. The problem part output data 26 of the second source code is output from the input / output device 14.

  FIG. 2 shows a first source code, a first problem part output data example generated by analyzing it, a second source code, and a second problem part output data example generated by analyzing it. FIG. The second source code 24 is a revised version of the source program that has been updated by adding a part of the first source code 21 and updating it.

  The first source code 21 includes file names a. c, and has a subroutine void func01 of 1-3 lines and a subroutine void func02 of 5-9 lines. Here, a subroutine is a block of source code that describes a series of processing, and includes methods, functions, and the like. The description of processing in each subroutine is omitted.

  The development support apparatus shown in FIG. 1 analyzes the first source code 21 to detect a problem part where a problem is suspected, and generates first problem part output data 22. In the example of FIG. 2, the description “a + b> c” in the parenthesis of the if statement in the seventh line in the subroutine void func02 of the first source code 21 is judged to be suspected because there is no parenthesis on the left side of the inequality sign. And detected as a problem. As a result, the first problem part output data 22 of the first source code 21 includes “ac” as the file name FILE, “seventh line” as the problem part line number 30 identifying the problem part, and the problem. As the problem indication sentence 32 describing the suspected reason, the data of the problem part having “error in if sentence” is included. In the following figures, comments such as “no NG parentheses” are written in the source code where the problem is suspected to facilitate understanding.

  On the other hand, the second source code 24 is updated by adding the code 41 on the third and fourth lines in the subroutine void func01 of the first source code 21. As a result, the line number of the subroutine void func02 is changed to line 7-11, but the source code in the subroutine void func02 is not changed.

  The development support apparatus shown in FIG. 1 analyzes the second source code 24 to detect a problematic part where the problem is suspected, and “ac” as the file name FILE and “problem part line number 30 identifying the problematic part” 9th line ", the second problem location output data 26 including the data of the problem location having" error in if statement "is output as the problem indication statement 32 describing the reason why the problem is suspected.

  However, since the second source code 24 has only the additional code 41 of line numbers 3 and 4 added to the subroutine void func01 in the first to third lines in the first source code 21, The subroutine void func02 on the 5th to 9th lines in the source code 21 and the subroutine void func02 on the 7th to 11th lines in the second source code 24 are substantially the same, although the line numbers are different. Therefore, the problem part of the second problem part output data 26 is different from the problem part of the first problem part data 22 only in the problem part line number 30, and the problem part is substantially the same and is duplicated. Yes.

  Therefore, the development support program according to the present embodiment uses the second problem location output data 26 to identify a problem location that overlaps the first problem location output data 22 obtained by analyzing the first source code as described above. Process to be excluded from.

  FIG. 3 is a flowchart showing a process of development support using the development support program in the present embodiment. First, the user who uses the development support program develops the first source code 21 (S1). The language of the source code may be any programming language such as a subroutine, C language, JAVA (registered trademark, programming language developed by Sun Microsystems), Visual Basic (programming language of Microsoft).

  Next, the development support apparatus of FIG. 1 analyzes the first source code 21, detects a problem part suspected of having a problem in the first source code 21, and includes the problem part and a problem indication sentence. First problem location output data 22 is output (S2). A specific example of the problem location output data is as described in FIG.

  The user changes, adds and updates a part of the first source code, and develops the revised second source code 24 (S3). The revised second source code 24 matches the first source code before the revision in a part where the change or addition is not performed, and the first part before the revision in the other part where the change or addition is performed. Does not match the source code.

  Then, the development support apparatus analyzes the second source code 24, detects a problem part suspected of having a problem in the second source code 24, and detects the second problem including the problem part and the problem indication sentence. The location output data 26_1 is output (S4). The problem part output data 26_1 of the second source code includes problem part output data for a part that has not been changed or added (old problem part output data) and a problem part for another part that has been changed or added. Output data (new problem location output data). Therefore, the old problem part output data is data that overlaps with the problem part output data of the first source code, and the cause is checked in the debugging process of the first source code 21 and it is confirmed that there is no problem. It is a place.

  Therefore, the development support apparatus excludes from the problem part 26_1 of the problem part output data of the second source code, the problem part that overlaps with the problem part included in the problem part output data 22 of the first source code (S5). . As a result, the development support apparatus needs to newly check whether there is a problem by excluding the problem part of the problem part output data of the first source code as the problem part output data for the second source code. The problem part data including only

  The development support program according to the present embodiment causes the computer to execute steps S4 and S5 in FIG. 3 so that the problem location output data including the new problem location of the second source code updated from the first source code is obtained. Is output.

  FIG. 4 is a flowchart of the processes of steps S4 and S5 of the development support program in the present embodiment. 4, steps S41 to S45 are processes corresponding to step S4 in FIG. 3, and processes S51 to S54 are processes corresponding to step S5 in FIG.

  The development support apparatus executes the development support program, parses the second source code, and detects a problem part (second problem part) that is suspected of having a problem in the second source code (S41). . Problems that are suspected of having a problem include, for example, problems that have doubts such as grammatical errors, variable definition errors, lack of memory area release processing acquired during program execution, and logical errors.

  Then, when the development support apparatus executes the development support program and detects the second problem location (YES in S42), the development support device generates a problem indication statement that points out the reason for detecting the second problem location (S43). ). Further, the development support apparatus executes the development support program, and the second description specifying information for specifying the description of the source code from the top of the subroutine including the detected second problem location to at least the second problem location. Is generated (S44).

  Preferably, the second description specifying information is either a hash value or an encoded code of a description (specification target description) from the top of the subroutine in which the second problem part is described to at least the second problem part. And preferably information having a smaller data amount than the description of the specific object. Further, the second description specifying information may be a description of the source code itself from the top of the subroutine in which the second problem part is described to at least the second problem part.

  Then, the development support apparatus executes the development support program and repeats the above steps S41 to S44 until all the descriptions of the second source code are executed (S45). As a result, the development support apparatus outputs the second problem location output data 26_1 of the second source code of FIG.

  FIG. 5 is a diagram illustrating step S44 in FIG. In FIG. 5, as an example of the second source code 24, a subroutine void func02 is shown on the first line, and the if statement on the fourth line in the subroutine void func02 is detected as a problem location. In this case, the development support device executes the development support program, and the description from the first line to the problem part on the fourth line of the subroutine void func02 is set as the specific description 34_1 for identifying the problem part, and the specific description 34_1. Is generated as the description specifying information 34. In the example of FIG. 5, the description specifying information 34 is “415fe51dbefb5. As described above, the description specifying information 34 may be an encoded code other than the hash value of the specific description 34_1, or may be data of the description itself.

  FIG. 5 shows an example of the second problem location output data 26 generated for the second source code 24. The second problem part output data 26 includes a file name FILE, a problem part line 30, a problem indication sentence 32, and description specifying information 34. However, the description specifying information 34 does not necessarily have to be included in the problem location output data 26 and may be associated with the file name FILE, the problem location line 30, and the problem indication sentence 32.

FIG. 6 is a diagram for explaining a method for detecting a subroutine including a problematic part in step S44. The development support apparatus executes a development support program, performs syntax analysis using BNF (Backus-Naur form), and detects a subroutine including a problem portion. FIG. 6 shows a BNF 50 of a method which is a kind of subroutine. The BNF 50 stipulates that a method declaration statement (MethodDeclaration) has the following syntax.
MethodDeclaration: Type MethodName '(' FormalParameterListopt ')'{'BlockStatementsopt'}'
Therefore, the development support apparatus parses the second source code 24, decomposes it into elements in the source code, and detects the description of the element group that matches the declaration statement of the method. FIG. 5 shows a table 51 in which the description of the declaration statement of the detected method is broken down into elements. Thus, when a source code element group that matches the method declaration statement by the BNF definition is detected, the source code is determined as a method declaration statement. By performing syntax analysis using such BNF, it is possible to detect a subroutine including a problem portion.

  Returning to FIG. 4, steps S51 to S54 corresponding to step S5 of the development support program will be described. The development support apparatus executes the development support program, whereby the second description specifying information 34 corresponding to the second problem location of the second source code detects the first source code detected by analyzing the first source code. It is checked whether it matches any of the first description specifying information corresponding to the problem part (S51). Then, when the second description specifying information of the second problem location matches any of the first description specifying information of the first problem location (YES in S52), the development support apparatus determines the matching second The second problem location corresponding to the description specifying information is excluded from the second problem location output data (S53). Then, the development support apparatus executes the above steps S51-S53 for all the second problem locations (S54).

  In order to execute the above step S51, when the development support apparatus analyzes the first source code and detects the first problem location, the development support apparatus identifies the first description corresponding to the first problem location. Generate information. This first description specifying information is preferably included in the output data in association with the first problem location.

  The reason why the description specified by the description specifying information is the description from the beginning of the subroutine to at least the problem part is as follows. In other words, the if statement at the problem location shown in FIG. 2 is included in the subroutine void func02, and its grammatical error, definition error, logical contradiction, etc. generally depend on the description before the if statement at the problem location. It is. Therefore, it is not always necessary to compare the description from the beginning to the end of the subroutine including the problem part with the description specifying information corresponding to the problem part of the first source code as the description of the specification target. If the description from the beginning to the end of the subroutine containing the problem location is a description specified by the specific description information, not only does the data amount of the specific description information increase, but also the description that does not directly affect the problem location after the problem location. When a change or addition is made, even if the problem part corresponds to the substantially same problem, it is detected as a new problem part that was not detected in the first source code.

  However, if the description of the problem location is included in the repetitive control description (specifically, a loop statement), the repetitive control including the description of the problem location from the beginning of the subroutine in which the problem location is described as description specifying information. Information that specifies the description up to the end of the description (loop statement). In the case of a loop statement, the description after the problem part affects the description of the problem part. Even in the case of the description up to the end of this loop statement, the description of the specific target is less than the description from the beginning to the end of the subroutine, and even if corrections or additions are made after the loop statement, it is substantially t The same problem can be detected.

[First and second source code examples]
FIG. 7 is a diagram showing a first example of the first and second source codes and the first and second problem location output data in the present embodiment. FIG. 7 shows examples of the first and second source codes 21 and 24 analyzed by the development support program of FIGS. 3 and 4 and the generated first and second problem part output data 22 and 26. An example is shown. In this example, a process for excluding a problem location that overlaps with the first problem location output data 22 from the second problem location output data 26 will be described.

  The first source code 21 has an if statement on the seventh line and an if statement on the twelfth line as a problem part where a problem is suspected. The if statement on the 7th line is a description in the subroutine void func02 on the 5th line, and the if statement on the 12th line is a description in the subroutine void func03 on the 10th line.

  Therefore, the development support apparatus executes the development support program, so that the file name “ac”, the problem location line “7th line”, and the problem are output as the first problem location output data 22_1 for the “if” statement on the 7th row. Data including an indication sentence “error in if sentence” is generated, and description specific information “415fe51dbefb5. This description specifying information is a hash value of the description 34_1 from the first 5th line to the 7th problem area of the subroutine void func02 including the if statement in the 7th line in the first source code 21.

  Further, the development support apparatus executes the development support program, so that the file name “ac”, the problem location line “12th line”, the problem as the first problem location output data 22_2 for the if statement on the 12th line. Data including the indicated sentence “error in if sentence” is generated, and the description specifying information “28ac3741de65...” Corresponding thereto is generated. This description specifying information is a hash value of the description 34_2 from the first 10th line to the problem part on the 12th line of the subroutine void func03 including the if statement on the 12th line in the first source code 21.

  On the other hand, in the second source code 24, a description 42 in the third and fourth lines and a description 42 in the fourteenth line are added to the first source code 21. Accordingly, the second source code 24 has an if statement on the ninth line and an if statement on the fifteenth line as a problem portion where the problem is suspected. The if statement on the 9th line is a description in the subroutine void func02 on the 7th line, and the if statement on the 15th line is a description in the subroutine void func03 on the 12th line.

  Therefore, the development support apparatus executes the development support program, so that the file name “ac”, the problem location line “9th line”, and the problem are output as the second problem location output data 26_1 for the “if” statement on the 9th line. Data including an indication sentence “error in if sentence” is generated, and description specific information “415fe51dbefb5. This description specifying information is a hash value of the description 34_3 from the first 7th line to the 9th line problem part of the subroutine void func02 including the if statement in the 9th line in the second source code 24.

  Further, the development support apparatus executes the development support program, so that the file name “ac”, the problem location line “15th line”, the problem as the second problem location output data 26_2 for the if statement on the 15th line. Data including the indication sentence “error in if sentence” is generated, and description specific information “13fe28dd5690...” Corresponding to the data is generated. This description specifying information is a hash value of the description 34_3 from the first 12th line to the 15th problem part of the subroutine void func03 including the if statement on the 15th line in the second source code 24.

  Therefore, the development support apparatus executes the development support program, and performs a process of excluding duplicate problem portions in S51 to S54 in FIG. That is, the development support apparatus checks whether or not the description specifying information of the second problem location output data 26_1 matches the description specification information of the first problem location output data 22_1 and 22_2 (S51). . In the example of FIG. 7, it is detected that the description specifying information “415fe51dbefb5...” Of the second problem location output data 26_1 matches the description specification information of the first problem location output data 22_1. As a result, the second problem location output data 26_1 for the if statement on the ninth line is excluded from the second problem location output data 26 (S53). In other words, the second problem location output data 26_1 is different in the line number from the first problem location output data 22_1, but the description specifying information matches, so the second problem location output data 26_1 and the first problem location output data 26_1 are output. It can be understood that the data 22_1 is output data obtained by detecting the same if sentence as the problem part.

  Next, the development support apparatus checks whether or not the description specifying information of the second problem location output data 26_2 matches the description specification information of the first problem location output data 22_1 and 22_2 (S51). ). In the example of FIG. 7, it is detected that the description specifying information “13fe28dd5690...” Of the second problem location output data 26_2 does not match the description specification information of the first problem location output data 22_2. That is, since the description 42 of the 14th line is added to the first source code 21 in the second source code 24, the description 42 of the 14th line may affect the if statement of the 15th line. The problem part for the if statement on the 15th line should not be excluded. Accordingly, the description specifying information does not match for the second problem location output data 26_2, and as a result, the second problem location output data 26_2 for the if statement on the 15th line is not excluded. It is included in the output data 26. In this way, the existence of the description 42 in the 14th line that affects the problem location for the second source code 24 is confirmed by the mismatch determination in the collation of the description specifying information, and the necessary problem location is excluded. Suppressed.

[Second and first source code examples]
FIG. 8 is a diagram showing a second example of the first and second source codes and the first and second problem location output data in the present embodiment. FIG. 8 shows an example of the first and second source codes analyzed by the development support program of FIGS. 3 and 4 and an example of the generated first and second problem location output data. . In this example, a process for excluding a problem location that overlaps with the first problem location output data from the second problem location output data will be described.

  In the example of FIG. 8, descriptions 43 in the sixth and seventh lines are added to the second source code 24 with respect to the first source code 21. However, this additional description 43 is a description after the if statement on the fourth line, and does not affect the problem of the if statement on the fourth line.

  In this case, the first problem indication output data 22_1 for the if statement in the fourth line is generated for the first source code 21, and the hash value of the specific description 34_1 including the description of the problem part in the fourth line is generated. Certain description specifying information “415fe51dbefb5...” Is generated. Further, the second problem indication output data 26_1 for the if statement on the fourth line is generated for the second source code 24, and the hash value of the specific description 34_3 including the description of the problem part on the fourth line. Description specific information “415fe51dbefb5...” Is generated. Since the specific descriptions 34_1 and 34_3 from the beginning of the subroutine void func02 including the problem part of the first and second problem indication output data match, the description specification information which is their hash value also matches. Yes. As a result, the second problem location output data 26_2 is excluded from the second problem location output data 26. In this example, the first and second problem part output data 22_1 and 26_1 are excluded because they all match the file name, line number, problem indication sentence, and description specifying information.

[Example where problem area is included in loop]
FIG. 9 is another diagram illustrating step S44 of FIG. FIG. 9 shows an example in which the subroutine void func02 is shown on the first line and the if statement on the fourth line in the subroutine void func02 is detected as a problem part as an example of the second source code 24. . In this example, the description of the problem part of the if statement on the fourth line is described in a loop composed of the for sentence on the third to fifth lines.

  In this case, the development support device executes the development support program and identifies the problem part from the first line of the subroutine void func02 to the seventh line of the last line of the loop including the problem part of the fourth line. And a hash value of the specific description 34_5 is generated as the description specifying information 34.

  FIG. 9 shows an example of the second problem location output data 26 generated for the second source code 24. The second problem part output data 26 includes description specifying information 34 in addition to the file name FILE, the problem part line 30, and the problem indication sentence 32. Alternatively, the description specifying information 34 is associated with the file name FILE, the problem part line 30, and the problem indication sentence 32. As described above, if the problem part is in the loop, the description in the loop may affect the problem part even if the description is added or changed after the problem part. Therefore, it is desirable that the description specified by the description specifying information 34 is from the top of the subroutine including the problem part to the last line of the loop including the problem part.

[Third first and second source code examples]
FIG. 10 is a diagram showing a third example of the first and second source codes and the first and second problem location output data in the present embodiment. FIG. 10 shows examples of the first and second source codes 21 and 24 analyzed by the development support program shown in FIGS. 3 and 4, and the generated first and second problem location output data 22 and 26. An example is shown. In this example, the problem part is described in a loop. In this example, a process for excluding a problem location that overlaps with the first problem location output data from the second problem location output data will be described.

  The first source code 21 has an if statement on the 8th line and an if statement on the 16th line as the problem part where the problem is suspected. The if statement on the 7th line is the description in the subroutine void func02 on the 5th line and the description in the loop on the 7th to 10th lines, and the if statement on the 12th line is the subroutine void func03 on the 10th line. This is a description in the loop of the 15th to 18th lines.

  Therefore, the development support apparatus executes the development support program, and as the first problem location output data 22_3 for the if statement on the 8th row, the file name “ac”, the problem location line “8th line”, the problem Data including an indication sentence “error in if sentence” is generated, and description specific information “415fe51dbefb5. This description specifying information is a hash value of the description 34_5 from the first 5th line of the subroutine void func02 including the if statement in the 8th line in the first source code 21 to the last 10th line of the loop statement.

  Further, the development support apparatus executes the development support program, so that the file name “ac”, the problem location line “16th line”, the problem as the first problem location output data 22_4 for the if statement on the 16th line. Data including the indicated sentence “error in if sentence” is generated, and the description specifying information “28ac3741de65...” Corresponding thereto is generated. This description specifying information is a hash value of the description 34_6 from the first 13th line of the subroutine void func03 including the if statement of the 16th line in the first source code 21 to the last 18th line of the loop statement.

  Note that the hash value of the description specifying information in the first problem location output data 22_3 and 22_4 is the same as the example of FIG. 7 for simplicity.

  On the other hand, the second source code 24 is generated by adding a description 44 in the third and fourth lines and a description 44 in the twentieth line to the first source code 21. Accordingly, the second source code 24 has an if sentence on the 10th line and an if sentence on the 18th line as a problem part where a problem is suspected. The if statement on the 10th line is the description in the subroutine void func02 on the 7th line, the description in the loop statement on the 9th to 12th lines, and the if statement on the 18th line is the subroutine void on the 15th line. This is a description in func03 and is in the loop statement on lines 17-21.

  Therefore, the development support apparatus executes the development support program, so that the file name “ac”, the problem location line “10th line”, the problem as the second problem location output data 26_3 for the if statement on the 10th line. Data including an indication sentence “error in if sentence” is generated, and description specific information “415fe51dbefb5. This description specifying information is a hash value of the description 34_7 from the first 7th line of the subroutine void func02 including the if statement of the 10th line in the second source code 24 to the last 12th line of the loop statement.

  Further, the development support apparatus executes the development support program, so that the file name “ac”, the problem location line “18th line”, the problem is output as the second problem location output data 26_4 for the if statement on the 18th line. Data including the indication sentence “error in if sentence” is generated, and description specific information “13fe28dd5690...” Corresponding to the data is generated. This description specifying information is a hash value of the description 34_8 from the first 15th line of the subroutine void func03 including the if statement in the 18th line in the second source code 24 to the last 21st line of the loop statement.

  Therefore, the development support apparatus executes the development support program, and performs a process of excluding duplicate problem portions in S51 to S54 in FIG. That is, the development support apparatus checks whether the description specifying information of the second problem location output data 26_3 matches the description specification information of any of the first problem location output data 22_3 and 22_4 (S51). . In the example of FIG. 10, it is detected that the description specifying information “415fe51dbefb5...” Of the second problem location output data 26_3 matches the description specification information of the first problem location output data 22_3. As a result, the second problem location output data 26_3 for the if statement on the 10th line is excluded from the second problem location output data 26 (S53). That is, the second problem location output data 26_3 is different in the line number from the first problem location output data 22_3, but the description specifying information matches. Therefore, the second problem location output data 26_3 and the first problem location output data 26_3 are output. It can be understood from the data 22_3 that the same if sentence is detected as a problem location.

  Next, the development support apparatus checks whether or not the description specifying information of the second problem location output data 26_4 matches the description specification information of any of the first problem location output data 22_3 and 22_4 (S51). ). In the example of FIG. 10, it is detected that the description specifying information “13fe28dd5690...” Of the second problem location output data 26_4 does not match the description specification information of the first problem location output data 22_4. That is, in the second source code 24, a description 45 on the 20th line is added to the first source code 21, and the description 45 is in the same loop statement as the problem part of the if statement on the 18th line. The description 45 may affect the “if” sentence on the 18th line, and the problematic part for the “if” sentence on the 18th line should not be excluded. Therefore, the description specific information does not match for the second problem location output data 26_4, and as a result, the second problem location output data 26_4 for the if statement on the 18th line is not excluded. It is included in the output data 26. In this way, the presence of the description 45 on the 20th line that affects the problem location for the second source code 24 is confirmed by the mismatch determination by collation of the description specifying information, and the necessary problem location is prevented from being excluded. doing.

[Fourth example of first and second source code]
FIG. 11 is a diagram showing a fourth example of the first and second source codes and the first and second problem location output data in the present embodiment. FIG. 11 shows examples of the first and second source codes 21 and 24 analyzed by the development support program shown in FIGS. 3 and 4 and the generated first and second problem location output data 22 and 26. An example is shown. In this example, if the target description of the problem part is the same, but is in a different subroutine, it is not excluded as a different problem part. In this example, a process for excluding a problem location that overlaps with the first problem location output data from the second problem location output data will be described.

  The first source code 21 has an “if” statement on the fourth line as a problem part in which a problem is suspected.

  Therefore, the development support apparatus executes the development support program, so that the file name “ac”, the problem location line “8th line”, the problem as the first problem location output data 22_5 for the if statement on the 4th line Data including an indication sentence “error in if sentence” is generated, and description specific information “415fe51dbefb5. This description specifying information is a hash value of the description 34_9 from the first line of the subroutine void func01 including the if statement of the fourth line in the first source code 21 to the if statement of the fourth line of the problem part. .

  On the other hand, the second source code 24 is generated by adding a subroutine void func02 in the first to sixth lines to the first source code 21. Accordingly, the second source code 24 has an if sentence on the 4th line and an if sentence on the 10th line as a problem part where a problem is suspected.

  Therefore, the development support apparatus executes the development support program, and as the second problem location output data 26_5 for the if statement on the 4th row, the file name “ac”, the problem location line “line 4”, the problem Data including the indicated sentence “error in if sentence” is generated, and the description specifying information “78ab09feffea...” Corresponding thereto is generated. This description specifying information is a hash value of the description 34_10 from the first line of the subroutine void func02 including the if statement of the fourth line in the second source code 24 to the fourth line of the if statement.

  Further, the development support apparatus executes the development support program, so that the file name “ac”, the problem location line “10th line”, the problem as the second problem location output data 26_6 for the if statement on the 10th line. Data including an indication sentence “error in if sentence” is generated, and description specific information “415fe51dbefb5. This description specifying information is a hash value of the description 34_11 from the first 7th line of the subroutine void func01 including the if statement of the 10th line in the second source code 24 to the 10th line of the if statement.

  Therefore, the development support apparatus executes the development support program, and performs a process of excluding duplicate problem portions in S51 to S54 in FIG. That is, the development support apparatus checks whether or not the description specifying information of the second problem location output data 26_5 matches the description specification information of the first problem location output data 22_5 (S51). In the example of FIG. 11, it is detected that the description specifying information “78ab09feffea...” Of the second problem location output data 26_5 does not match the description specification information of the first problem location output data 22_5. As a result, the second problem location output data 26_5 for the if statement on the fourth line from the second problem location output data 26 is not excluded. That is, the second problem location output data 26_5 has the same line number as the first problem location output data 22_5, but the description specifying information does not match, so the second problem location output data 26_5 and the first problem location output data 26_5 are the same. It can be understood that the problem part output data 22_5 has detected an if sentence of a different object as a problem part.

  Next, the development support apparatus checks whether the description specifying information of the second problem part output data 26_6 matches the description specifying information of the first problem part output data 22_5 (S51). In the example of FIG. 11, it is detected that the description specifying information “415fe51dbefb5...” Of the second problem location output data 26_6 matches the description specification information of the first problem location output data 22_5. That is, in the second source code 24, a description of the subroutine void func02 on the first to sixth lines is added to the first source code 21, and the subroutine void 1 to 6 in the first source code 21 is added. The description of func01 has moved to lines 7-12. Therefore, the description specifying information for the second problem location output data 26_6 is the same, and as a result, the second problem location output data 26_6 for the if statement on the 10th line is excluded, and the second problem location output data. 26 is not included.

[Fifth first and second source code examples]
FIG. 12 is a diagram showing a fifth example of the first and second source codes and the first and second problem location output data in the present embodiment. The first source code 21 has the “if” statement on the fourth line as a problem location where a problem is suspected.

  By executing the development support program, the development support apparatus executes, as the first problem code output data 22_6 for the if statement on the fourth line, the file name “ac”, the problem code, and the first source code 21. Data including the line “line 4” and the problem indication sentence “error in if sentence” is generated, and the description specifying information “78ab09feffea...” Corresponding to the data is generated. This description specifying information is a hash value of the description 34_12 from the beginning of the subroutine void func01 on the first line including the if statement on the fourth line in the first source code 21 to the fourth line of the problem location.

  On the other hand, in the second source code 24, a description 46 on lines 08-10 is added to the first source code 21. Then, for the second source code 24, the if sentence on the fourth line and the if sentence on the eighth line are detected as problem parts.

  That is, by executing the development support program, the development support apparatus executes, as the second problem code output data 26_7 for the if statement on the fourth line, the file name “ac”, Data including the problem part line “line 4” and the problem indication sentence “error in if sentence” is generated, and description specific information “78ab09feffea...” Corresponding to the data is generated. This description specifying information is a hash value of the description 34_13 from the first line of the subroutine void func01 including the if statement of the fourth line in the second source code 26 to the fourth line of the problem part.

  Further, the development support apparatus executes the development support program, thereby providing the second source code 24 with the file name “ac”, the problem as the second problem location output data 26_8 for the “if” statement on the eighth line. Data including the location line “line 8” and the problem indication sentence “error in if sentence” is generated, and the description specifying information “415fe51dbefb5...” Corresponding thereto is generated. This description specifying information is a hash value of the description 34_14 from the first line of the subroutine void func01 including the if statement of the eighth line in the second source code 24 to the eighth line of the problem part.

  Therefore, the development support apparatus executes the development support program, and performs a process of excluding duplicate problem portions in S51 to S54 in FIG. As a result, the description specifying information “78ab09feffea...” Of the second problem location output data 26_7 matches the description specification information “78ab09feffea...” Of the first problem location output data 22_6 and is excluded. In addition, the description specifying information “415fe51dbefb5...” Of the second problem location output data 26_8 is inconsistent with the description specifying information “78ab09feffea...” Of the first problem location output data 22_6 and is not excluded.

  As described above, even if the description 46 is added to the 8th to 10th lines of the second source code 24, the description specifying information of the “if” statement in the fourth line is the if statement in the fourth line of the first source code 21. Are excluded from the second problem location output data 26. Then, the problem location output data 26_8 for the “if” sentence in the description 46 added to the second source code 24 is not excluded from the second problem location data 26.

[Sixth first and second source code examples]
FIG. 13 is a diagram showing a sixth example of the first and second source codes and the first and second problem location output data in the present embodiment. The first source code 21 has an if statement on the 4th line and an if statement on the 7th line as a problem part where a problem is suspected.

  By executing the development support program, the development support apparatus executes, as the first problem code output data 22_7 for the if statement on the fourth line, the file name “ac” and the problem code for the first source code 21. Data including the line “line 4” and the problem indication sentence “error in if sentence” is generated, and the description specifying information “78ab09feffea...” Corresponding to the data is generated. This description specifying information is a hash value of the description 34_15 from the first line of the subroutine void func01 including the if statement of the fourth line in the first source code 21 to the fourth line of the problem part.

  Similarly, for the first source code 21, the development support apparatus uses the file name “ac” and the problem part line “seventh line” as the first problem part output data 22_8 for the “if” sentence on the seventh line. , The data including the problem indication sentence “error in the if sentence” is generated, and the description specifying information “31b409faf0e0...” Corresponding thereto is generated. This description specifying information is a hash value of the description 34_16 from the first line of the subroutine void func01 including the if statement of the fourth line in the first source code 21 to the seventh line of the problem part.

  On the other hand, in the second source code 24, a description 47 on lines 07-08 is added to the first source code 21. Then, for the second source code 24, the if sentence on the fourth line and the if sentence on the ninth line are detected as problem parts.

  By executing the development support program, the development support apparatus executes, as the second problem code output data 26_9 for the if statement on the fourth line, the file name “ac”, the problem code, and the second source code 24. Data including the line “line 4” and the problem indication sentence “error in if sentence” is generated, and the description specifying information “78ab09feffea...” Corresponding to the data is generated. This description specifying information is a hash value of the description 34_17 from the first line of the subroutine void func01 including the if statement of the fourth line in the second source code 24 to the fourth line of the problem part.

  Furthermore, the development support apparatus executes the development support program, so that the second source code 24 has the file name “ac”, the problem name as the second problem location output data 26_10 for the if statement on the ninth line. Data including a location line “9th line” and a problem indication sentence “error in if sentence” is generated, and corresponding description specifying information “415fe51dbefb5...” Is generated. This description specifying information is a hash value of the description 34_14 from the first line of the subroutine void func01 including the if statement of the 9th line in the second source code 24 to the 9th line of the problem part.

  Therefore, the development support apparatus executes the development support program, and performs a process of excluding duplicate problem portions in S51 to S54 in FIG. As a result, the description specifying information “78ab09feffea...” Of the second problem location output data 26_9 matches the description specification information “78ab09feffea...” Of the first problem location output data 22_7 and is excluded. In addition, the description specifying information “415fe51dbefb5...” Of the second problem location output data 26_10 is inconsistent with the description specification information “78ab09feffea...” Of the first problem location output data 22_8 and is not excluded.

  As described above, since the description 47 is added before the ninth line of the problem portion on the seventh to eighth lines of the second source code 24, the description specifying information of the “if” statement on the ninth line becomes the first source code. 21 is not excluded from the second problem location output data 26 because it is inconsistent with the description specifying information of the if statement on the seventh line.

  FIG. 14 is a second flowchart of the processes of steps S4 and S5 of the development support program in the present embodiment. FIG. 14 includes a step S51_B instead of the step S51 in the flowchart of FIG. The other steps are the same as those in FIG.

  According to the flowchart of FIG. 14, in step S51_B, the development support apparatus executes the development support program, and both the problem indication sentence in addition to the second description specifying information corresponding to the second problem location are The first source code is analyzed to check whether it matches either the first description specifying information corresponding to the first problem location detected and the problem indication sentence. If they match, the second problem location is excluded from the second problem location output data.

  That is, according to the processing of FIG. 14, when excluding duplicate problem parts from the problem part group obtained by analyzing the second source code, the description specifying information matches and the problem indication sentence matches. Also check what to do. By doing so, it is possible to prevent the newly detected problem part from being excluded in the following situation.

  For example, when the setting of the problem location detection item by the development support program is changed to a setting different from that when the first source code is analyzed, the problem location and the problem indication sentence obtained by analyzing the second source code are displayed. , The same if sentence may be newly detected. In such cases, the newly detected problem location and problem indication should not be excluded. In such a case, if the problem location to be excluded is determined by performing the processing of FIG. 14, the newly detected problem location and the problem indication sentence may be left in the second problem location output data. it can.

  In step S51_B of FIG. 14, it is determined whether or not the description specifying information corresponding to the problem location matches the problem indication text. The description specification information corresponding to the problem location, the problem indication text, and the file name are further determined. It is also possible to determine whether or not and match. In this case, when the same problem location, the same problem indication sentence, and the same description specifying information in the same file match, it is excluded from the second problem location output data.

[Seventh first and second source code examples]
FIG. 15 is a diagram showing a seventh example of the first and second source codes and the first and second problem location output data in the present embodiment. In this example, according to the flowchart of FIG. 14, it is possible to prevent the newly detected problem location and problem indication sentence data from the second problem location output data.

  The first source code 21 has the “if” statement on the fourth line as a problem location where a problem is suspected. By executing the development support program, the development support apparatus executes, as the first problem code output data 22_9 for the if statement on the fourth line, the file name “ac”, the problem code for the first source code 21. Data including the line “line 4” and the problem indication sentence “error in if sentence” is generated, and the description specifying information “78ab09feffea...” Corresponding to the data is generated. This description specifying information is a hash value of the description 34_19 from the first line of the subroutine void func01 including the if statement of the fourth line in the first source code 21 to the fourth line of the problem part.

  On the other hand, in the second source code 24, descriptions 48 in the first, second, third and ninth lines are added to the first source code 21. For the second source code 24, the if statement on the seventh line is detected as a problem location.

  The development support apparatus executes the development support program in which the “variable definition mistake” is added to the setting of the detection item when the first source code is analyzed. The setting is changed by the second source code developer. For the second source code 24, the development support device uses the file name “ac”, the problem part line “seventh line”, the problem indication as the second problem part output data 26_11 for the “if” sentence on the seventh line. Data including the sentence “error in if sentence” is generated, and corresponding description specifying information “78ab09feffea...” Is generated. This description specifying information is a hash value of the description 34_20 from the first 4th line of the subroutine void func01 including the if statement of the 7th line in the second source code 24 to the 7th line of the problem part.

  Furthermore, the development support apparatus uses the second source code 24 as the second problem location output data 26_12 because there is a possibility of a problem in the definition of the variable of the “if” statement on the seventh line. File name “ac”, problem part line “7th line”. Data including a problem indication sentence “error in variable a” is generated, and description specific information “78ab09feffea...” Corresponding to the data is generated. The problem location is the same if statement on the seventh line as described above, but the cause of this problem is the possibility of an error in the variable a of the if statement. Therefore, the description specifying information is a hash value of the description 34_20 from the first 4th line of the subroutine void func01 including the same if statement on the 7th line in the second source code 24 to the 7th line of the problem part, It is the same as the above description specifying information. In the second source code 24, the variable in the parenthesis of the subroutine void func01 on the fourth line is that the variable a is an integer having a normal number of bits, whereas the variables b and c are integers having a short number of bits. Is defined. Therefore, the problem indication sentence “error in variable a” as described above is detected because the precision of the integer of variable a is not a sign of the precision of the integers of variables b and c.

  Therefore, the development support apparatus executes the development support program, and performs a process of eliminating duplicate problem locations in S51 to S54 in FIG. As a result, the description specifying information “78ab09feffe... A” of the second problem location output data 26_11 matches the description specifying information “78ab09feffea... “Error in if sentence” also matches and is excluded. However, the description specifying information “78ab09feffea...” Of the second problem location output data 26_12 matches the description specifying information “78ab09feffea...” Of the first problem location output data 22_9. "Error in a" does not match and is not excluded from the second problem location output data.

  Thus, even if the problem location and the problem indication text detected for the first time by changing the analysis setting of the second source code 24 are the problem location output data for the same problem location, the problem indication text is different. In other words, if the reason for the problem is different, it is not excluded from the second problem location output data as a new problem location.

  The above embodiment is summarized as follows.

(Appendix 1)
Analyzing the second source code generated by updating the first source code to detect the second problem portion;
Generating second description specifying information for specifying a description from the top of a subroutine in which the second problem part is described to at least the second problem part;
The second description specifying information corresponding to the second problem location detected by analyzing the second source code corresponds to the first problem location detected by analyzing the first source code. The second problem location is excluded from the output target as the problem location of the second source code when the first description specifying information matches.
A computer-readable development support program that causes a computer to execute processing.

(Appendix 2)
In Appendix 1,
In the step of generating the second description specifying information, when the description of the second problem location is repeatedly included in the control description, the second problem location is described as the second description specification information. A development support program for generating description specifying information for specifying a description from the top of a subroutine to the end of the repetitive control description including a description of the second problem portion.

(Appendix 3)
In Appendix 1 or 2,
further,
Generating a second problem indication statement describing the problem of the second problem location;
As the output, the second problem location and the second problem indication sentence are output,
In the step of excluding from the output target, in addition to the second description specifying information being identical to the first description specifying information, the second problem indication sentence of the second problem location and the first description A development support program for excluding the second problem part from the output target when the first problem indication sentence corresponding to the problem part matches.

(Appendix 4)
In Appendix 3,
In the step of excluding from the output target, the second description specifying information matches the first description specifying information, and the second problem indicating sentence matches the first problem indicating sentence. In addition, when the file name of the second source code matches the file name of the second source code, the development support program excludes the second problem portion from the output target.

(Appendix 5)
In Appendix 1 or 2,
The first and second description specifying information is either a hash value or an encoded code of a description of a source code that is a specified target, and has a smaller data amount than a description of the source code that is the specified target. Development support program.

(Appendix 6)
In Appendix 1 or 2,
In the step of excluding from the output target, the second description specifying information is any of the first description specifying information corresponding to the plurality of first problem points detected by analyzing the first source code. And the second description specifying information corresponding to the plurality of first problem locations is excluded from the output target, and the second description specifying information corresponding to the plurality of first problem locations is excluded. A development support program to be included in the output target when it does not match all of the above.

(Appendix 7)
In Appendix 1 or 2,
The subroutine is a source code block describing a series of processing, and is a development support program including methods and functions.

(Appendix 8)
In Appendix 1 or 2,
A development support program for detecting a problem location when there is a problem in the source code based on a set analysis target in the step of detecting the problem location.

(Appendix 9)
Analyzing the second source code generated by updating the first source code to detect the second problem portion;
Generating second description specifying information for specifying a description from the top of a subroutine in which the second problem part is described to at least the second problem part;
The second description specifying information corresponding to the second problem location detected by analyzing the second source code corresponds to the first problem location detected by analyzing the first source code. The second problem location is excluded from the output target as the problem location of the second source code when the first description specifying information matches.
Development support method having processing.

(Appendix 10)
In Appendix 9,
In the step of generating the second description specifying information, when the description of the second problem location is repeatedly included in the control description, the second problem location is described as the second description specification information. A development support method for generating description specifying information for specifying a description from the top of a subroutine to the end of the repetitive control description including the description of the second problem portion.

(Appendix 11)
Means for analyzing the second source code generated by updating the first source code and detecting the second problem location;
Means for generating second description specifying information for specifying a description from the top of a subroutine in which the second problem part is described to at least the second problem part;
The second description specifying information corresponding to the second problem location detected by analyzing the second source code corresponds to the first problem location detected by analyzing the first source code. And a means for excluding the second problem part from the output target as the problem part of the second source code when the first description specifying information matches.

20: Development support program 21: First source code 22: Problem portion output data of first source code 24: Second source code 26: Problem portion output data of second source code 30: Problem portion 32: Problem Indicator 34: Description specific information

Claims (8)

Analyzing the second source code generated by updating the first source code to detect the second problem portion;
Generating second description specifying information for specifying a description from the top of a subroutine in which the second problem part is described to at least the second problem part;
The second description specifying information corresponding to the second problem location detected by analyzing the second source code corresponds to the first problem location detected by analyzing the first source code. The second problem location is excluded from the output target as the problem location of the second source code when the first description specifying information matches.
A computer-readable development support program that causes a computer to execute processing. In claim 1,
In the step of generating the second description specifying information, when the description of the second problem location is repeatedly included in the control description, the second problem location is described as the second description specification information. A development support program for generating description specifying information for specifying a description from the top of a subroutine to the end of the repetitive control description including a description of the second problem portion. In claim 1 or 2,
further,
Generating a second problem indication statement describing the problem of the second problem location;
As the output, the second problem location and the second problem indication sentence are output,
In the step of excluding from the output target, in addition to the second description specifying information being identical to the first description specifying information, the second problem indication sentence of the second problem location and the first description A development support program for excluding the second problem part from the output target when the first problem indication sentence corresponding to the problem part matches. In claim 3,
In the step of excluding from the output target, the second description specifying information matches the first description specifying information, and the second problem indicating sentence matches the first problem indicating sentence. In addition, when the file name of the second source code matches the file name of the first source code , the development support program excludes the second problem portion from the output target. In claim 1 or 2,
The first and second description specifying information is either a hash value or an encoded code of a description of a source code that is a specified target, and has a smaller data amount than a description of the source code that is the specified target Development support program. In claim 1 or 2,
In the step of excluding from the output target, the second description specifying information is any of the first description specifying information corresponding to the plurality of first problem points detected by analyzing the first source code. And the second description specifying information corresponding to the plurality of first problem locations is excluded from the output target, and the second description specifying information corresponding to the plurality of first problem locations is excluded. A development support program to be included in the output target when it does not match all of the above. Analyzing the second source code generated by updating the first source code to detect the second problem portion;
Generating second description specifying information for specifying a description from the top of a subroutine in which the second problem part is described to at least the second problem part;
The second description specifying information corresponding to the second problem location detected by analyzing the second source code corresponds to the first problem location detected by analyzing the first source code. The second problem location is excluded from the output target as the problem location of the second source code when the first description specifying information matches.
Development support method having processing. Means for analyzing the second source code generated by updating the first source code and detecting the second problem location;
Means for generating second description specifying information for specifying a description from the top of a subroutine in which the second problem part is described to at least the second problem part;
The second description specifying information corresponding to the second problem location detected by analyzing the second source code corresponds to the first problem location detected by analyzing the first source code. And a means for excluding the second problem part from the output target as the problem part of the second source code when the first description specifying information matches.

Images