JP5024252B2 - Trace information acquisition device, trace information acquisition program, and trace information acquisition method - Google Patents

Description

  The present invention relates to a trace information acquisition device, a trace information acquisition program, and a trace information acquisition method.

  When trace information is acquired during loop execution, trace information with the same pattern may be output repeatedly. In this case, a large trace storage area is required, and analysis becomes difficult. Or the information is overwritten and lost. In order to solve this, the following techniques have been proposed.

  Patent Document 1 describes a history registration control circuit that suppresses history registration when a predetermined specific pattern of microinstruction words is detected. Patent Document 2 discloses a trace mask control circuit that ends a trace at the end of the first loop and restarts the trace at the end of the last loop.

JP-A-57-19854 JP-A-11-73344

  The trace pattern during loop execution changes. Therefore, the specific pattern in Patent Document 1 cannot be determined in advance in many cases. In Patent Document 2, there is a problem that trace information of a pattern that newly appears in the second and subsequent loops is lost.

  An object of this invention is to provide the trace information acquisition apparatus, the trace information acquisition program, and the trace information acquisition method for solving the subject mentioned above.

A trace collection device according to an embodiment of the present invention includes a trace buffer that sequentially stores trace data generated by execution of a traced process, a first pattern table, a memory that stores a first analysis buffer, Each trace data (first section data) generated by each execution of the first loop in the traced process is input, and the first section data is already stored in the first pattern table. If no coincidence (pattern coincidence) with any of the first section data that has been performed is detected, the input first section data is added to the first pattern table and the first analysis buffer, and the pattern When a match is detected, at least a part of the first interval data is not stored in the first analysis buffer, and when the end of the first loop is detected, the first analysis buffer is detected. The contents of the file comprises analyzing section for output to the trace buffer.
A trace collection program according to an embodiment of the present invention includes a trace buffer that sequentially stores trace data generated by execution of a process to be traced, a first pattern table, and a memory that stores a first analysis buffer. Each trace data (first section data) generated by each execution of the first loop in the traced process is input to the computer, and the first section data is the first pattern. If a match (pattern match) with any of the first section data already stored in the table is not detected, the input first section data is added to the first pattern table and the first analysis buffer. When the pattern match is detected, at least part of the first section data is not stored in the first analysis buffer, and the end of the first loop is detected. Then, to execute an analysis unit for outputting the contents of said first analysis buffer to the trace buffer.

A trace collection method according to an embodiment of the present invention includes a trace buffer that sequentially stores trace data generated by execution of a traced process, a first pattern table, and a memory that stores a first analysis buffer. The computer inputs each of the trace data (first section data) generated by each execution of the first loop in the traced process, and the first section data is the first pattern. If a match (pattern match) with any of the first section data already stored in the table is not detected, the input first section data is added to the first pattern table and the first analysis buffer. When the pattern match is detected, at least a part of the first section data is not stored in the first analysis buffer,
When the end of the first loop is detected, there is an analysis step of outputting the contents of the first analysis buffer to the trace buffer.

  It is possible to acquire trace information of different sequences while preventing a large amount of trace information of the same sequence from being output in large quantities during loop execution in which the pattern changes.

  FIG. 1 is a configuration diagram of a trace collection apparatus 10 according to the first embodiment of the present invention. The trace collection apparatus 10 includes a trace file 12, a generation unit 14, an analysis unit 15, an output unit 16, and a memory 20. The memory 20 stores a loop management table 21, a level storage area 22, and a trace area 23. The memory 20 may store a trace processing program 24 and a trace collection program 25.

  The generation unit 14 generates a trace data 30 by executing a process to be traced (process to be traced) and outputs the trace data 30 to the analysis unit 15. The generation unit 14 is a device control device or the like, and is realized by hardware. The generation unit 14 may also be realized by the processor 13 of the trace collection device 10 that is the computer 11 executing the trace processing program 24 that performs business processing and the like.

  The analysis unit 15 inputs the trace data 30 and sequentially stores it in the trace area 23. However, the analysis unit 15 records the pattern generated during the loop execution of the traced process in the loop management table 21 and does not store the trace information of the same pattern in the trace area 23 during the subsequent loop execution.

  The output unit 16 outputs the trace data 30 stored in the trace area 23 to the trace file 12 periodically or when the usage rate of the trace area 23 is high. The output unit 16 may not be provided.

  The analysis unit 15 and the output unit 16 are realized by hardware. The analysis unit 15 or the output unit 16 may be realized by the processor 13 of the trace collection device 10 that is the computer 11 executing the trace collection program 25.

  The level storage area 22 stores the number of nesting levels of loops during execution of the traced process (the number of layers in the inclusion relationship). When the traced process is not being executed in a loop, this value is 0, for example. During execution of the outermost loop (first loop), the level storage area 22 stores, for example, 1. During execution of the inner loop (second loop) that is nested in the first loop, the level storage area 22 stores, for example, 2. Thereafter, each time the number of executing loops increases, the level storage area 22 stores a value one more. The initial value of the level storage area 22 is zero.

  FIG. 2 shows the configuration of the trace data 30. The trace data 30 includes a type 31 and additional data 32. The type 31 indicates the type of event for which the trace data 30 is generated. The type 31 is, for example, loop entry, loop exit, loop pattern, other event notification, or the like. The loop entry and loop exit indicate the start and end of each loop.

  The loop pattern indicates execution at the top of the loop. That is, the loop pattern indicates the start and end of each execution of the loop. In the present invention, a set of trace data 30 generated by one execution of a loop is interval data. The section data is a set of trace data 30 from a loop pattern indicating the start of execution of a certain loop to immediately before the loop pattern indicating the start of execution of the next loop. Alternatively, the section data is a set of trace data 30 from a loop pattern indicating the start of execution of a certain loop to immediately before a loop exit indicating the end of the loop.

  Other event notification is trace data 30 for notifying the occurrence of an event other than the above. Other event notifications include, for example, routine entry / routine exit (general function call start / end), MPI entry / MPI exit (MPI function call start / end), send (message transmission), and the like. Here, MPI means Message Passing Interface.

  The additional data 32 is detailed notification data corresponding to the event to be notified. The additional data 32 of loop entry, loop exit, and loop pattern includes a loop identifier and the like. The additional data 32 of other event notification includes a function name, a parameter value, and the like.

  FIG. 3 shows a source code example (1) of the trace processing program 24. The trace processing program 24 is a program (a right side in the figure) in which, for example, a trace function call is inserted into a program including a loop (a left side in the figure). When the trace function is executed by the processor 13, for example, the trace data 30 having the same type 31 as the function name is generated. For example, when the processor 13 executes the loop_entry function, the trace data 30 of the loop entry is generated. Note that the MPI entry, MPI exit, and send trace data 30 are generated by the MPI_send function.

  As is apparent from the figure, the loop_entry function and the loop_exit function are inserted at positions immediately before and after the start of the loop. The loop_pattern function is inserted immediately before the first execution instruction in the loop. The routine_entry function and routine_exit function are inserted immediately before and after the function call (in this figure, calc1 function and calc2 function call). A dedicated tool or compiler analyzes the context of the source program of the traced program 24 and automatically inserts a trace function. The programmer may insert it manually.

  The additional data 32 may be input as a parameter of the trace function, or may be generated in the trace function.

  The trace data 30 may be directly generated by the trace processing program 24 regardless of the trace function. For example, an instruction for generating the trace data 30 may be inserted into the object program when the compiler compiles the source program (the left side in the figure) of the trace processing program 24.

  FIG. 4 is a diagram showing the configuration of the trace area 23. The trace area 23 includes a trace buffer 40 and an area pointer 41. The trace buffer 40 stores the trace data 30 sequentially. The trace buffer 40 is usually a circular buffer. The area pointer 41 points to the start address of the empty area of the trace buffer 40. The initial value is the top address of the trace buffer 40.

  When adding the trace data 30 to the trace buffer 40, the analysis unit 15 first stores the trace data 30 after the area indicated by the area pointer 41. After the storage, the same part stores the address immediately after the additional data (when it is full, the head address of the trace buffer 40) in the area pointer 41.

  FIG. 5 shows the configuration of the loop management table 21. The loop management table 21 exists corresponding to each level of loop nest. That is, the loop management table 21 exists corresponding to each of one or more values in the level storage area 22. The loop management table 21 corresponding to each level includes an analysis buffer 50, a buffer pointer 51, a pattern table 52, and a table pointer 53.

  The analysis buffer 50 stores the trace data 30 sequentially. The initial value of the analysis buffer 50 is, for example, zero. The buffer pointer 51 points to the start address of the free area of the analysis buffer 50. The initial value of the buffer pointer 51 is the start address of the analysis buffer 50.

  When the analysis unit 15 adds the trace data 30 to the analysis buffer 50, the analysis unit 15 stores the trace data 30 after the area indicated by the buffer pointer 51, and stores the address immediately after the additional data in the buffer pointer 51 after the storage. To do.

  The pattern table 52 sequentially stores the pattern ID 54 and the pattern data 55 in association with each other. The initial value of the pattern table 52 is, for example, zero. The pattern data 55 is section data, that is, a set of trace data 30. The pattern data 55 may include other data. The table pointer 53 points to the start address of the empty area of the pattern table 52. The initial value of the table pointer 53 is the start address of the pattern table 52.

  When adding the pattern data 55 to the pattern table 52, the analysis unit 15 stores the pattern data 55 after the area indicated by the table pointer 53, and stores the address immediately after the additional data in the table pointer 53 after the storage. To do.

  The loop management table 21 corresponding to the first loop includes a first analysis buffer 61 and a first pattern table 62. The loop management table 21 corresponding to the second loop includes a second analysis buffer 63 and a second pattern table 64. Here, the first loop refers to the outermost loop, and is a loop whose loop nest level (value of the level storage area 22) is 1. The second loop refers to a loop nested within the first loop, and is a loop having a loop nesting level of 2.

  The loop management table 21, the analysis buffer 50, and the pattern table 52 corresponding to the value (1 or more) of the level storage area 22 at a certain point in time are the loop management table 21, the analysis buffer 50, and the pattern at the current level. Called Table 52. For example, if the value of the level storage area 22 is 1 at a certain time, the analysis buffer 50 at the current level at that time is the first analysis buffer 61. If the value of the level storage area 22 is 2 at a certain time, the analysis buffer 50 at the current level at that time is the second analysis buffer 63.

  FIG. 6 is an operation flowchart of the analysis unit 15. First, the analysis unit 15 determines the type 31 of the trace data 30 input from the generation unit 14 (S1).

  If the type 31 is other event notification, the same part determines the loop nest level (value of the level storage area 22) (S5). If the level is 0 (Y in S5), the same section adds the input trace data 30 to the trace buffer 40 (S6) and ends the operation. If the level is not 0 (N in S5), the same section adds the input trace data 30 to the analysis buffer 50 at the current level (S9) and ends the operation. That is, the analysis unit 15 appends the input trace data 30 to the analysis buffer 50 at the current level if the generation unit 14 is executing a loop, and to the trace buffer 40 if the generation unit 14 is not executing the loop.

  When the type 31 is loop start, the analysis unit 15 traces the input trace data 30 to the analysis buffer 50 at the current level if the generation unit 14 is executing a loop, and traces the input trace data 30 if the generation unit 14 is not executing the loop. The information is added to the buffer 40 (S5, S6, S9). Thereafter, the same unit adds 1 to the value in the level storage area 22, and initializes the loop management table 21 at the current level (S8). The initialization of the loop management table 21 includes initialization of the buffer pointer 51, the table pointer 53, the analysis buffer 50, and the pattern table 52.

  When the type 31 is loop head execution, the analysis unit 15 determines whether or not the analysis buffer 50 at the current level is empty (initial state) (S2). If it is not empty (N in S2), the same part executes the same pattern detection process (see FIG. 7) (S3). If it is empty (Y in S2), the same part skips the same pattern detection process. This skip occurs when the trace data 30 indicating the first loop head execution following the start of the loop is input. Thereafter, the same section adds the input trace data 30 to the analysis buffer 50 at the current level (S4), and ends the operation.

  When the type 31 is loop end, the analysis unit 15 executes the same pattern detection process (see FIG. 7), adds the input trace data 30 to the analysis buffer 50 at the current level, and subtracts 1 from the value in the level storage area 22. (SA, SB, SC). Thereafter, the same part determines the level of the loop nest (level storage area 22 value) (SD). If the level is 0 (Y in SD), the same part adds the contents of the first analysis buffer 50 to the trace buffer 40 (SE) and ends the operation. If the level is not 0 (N in SD), the same part adds the contents of the analysis buffer 50 of the original level to the analysis buffer 50 of the current level (SF) and ends the operation.

  FIG. 7 is an operation flowchart of the same pattern detection processing portion of the analysis unit 15. If the pattern table 52 at the current level is empty (initial value) (Y in S11), the analysis unit 15 performs registration processing in the pattern table 52. The pattern table 52 at the current level is empty (initial value) when the trace data 30 indicating the second loop head execution is input after the start of the loop, that is, when the initial execution of the loop is completed. To do.

  The same part generates a pattern ID 54 and adds it to the pattern table 52 (S12). The pattern ID 54 is generated, for example, by adding a unique serial number to the trace collection device 10 to the loop identifier (processing loop identifier) in the additional data 32 included in the trace data 30 indicating the input loop head execution.

  Thereafter, the same part adds the trace data 30 of the analysis buffer 50 at the current level after the latest section start data to the pattern data 55 of the pattern table 52. The latest section start data is trace data 30 indicating the latest (previous) loop head execution having the same loop identifier as the loop identifier being processed (S13). That is, the same part adds the latest section data to the pattern table 52. The latest section data is section data generated by the latest execution of the loop. At this time, the same part may additionally write data indicating the end of the latest section data to the pattern data 55. For example, the same part may add the size of the latest section data immediately after the pattern ID 54. Alternatively, the same part may add a delimiter (such as a value that cannot be generated as the pattern data 55) to the end of the section data.

  The same part adds the pattern ID 54 to the latest section start data of the analysis buffer 50 at the current level (S14), and ends the same pattern detection process. The addition of the pattern ID 54 is performed, for example, by rewriting the loop identifier in the additional data 32.

  If the pattern table 52 at the current level is not empty (N in S11), the analysis unit 15 determines whether the latest section data and the section data registered in the pattern table 52 match each other (S15). The same section sequentially acquires the section data registered in the pattern table 52, and sequentially compares each trace data 30 in the section data with each trace data 30 in the latest section data from the head, and the patterns all match. The section data registered in the table 52 (matching section data) is searched. At this time, the same part may compare all of the type 31 and the additional data 32 of the trace data 30 to be compared. The same unit may compare only type 31 or only part of type 31 and additional data 32 (for example, a specific parameter value).

  If the matching section data is found (Y in S16), the same part adds the pattern ID 54 of the matching section data to the latest section start data of the analysis buffer 50 at the current level (S17). The pattern ID 54 indicates that the trace data 30 of the pattern with the pattern ID 54 has been generated. Next, the same part returns the value of the buffer pointer 51 to indicate the next address of the trace data 30 (S18), and ends the same pattern detection process. That is, the same unit discards (overwrites with subsequent data) data other than the latest section start data in the latest section data.

  When the matching section data cannot be found (N in S16), the same part performs a registration process to the pattern table 52 (S12, S13, S14).

  The following is a description according to a specific example of the operation of the present embodiment. FIG. 8 shows an example (1) of the trace data 30 generated when the processor 13 executes the example (1) of the trace processing program 24 shown in FIG. Assume that the variable N in the program is 2. Note that the serial number 33 shown in FIG. 8 is described for reference, and is not necessarily actually generated data. The same applies to the subsequent drawings, and the serial number 33 is not necessarily stored in the trace buffer 40 or the pattern table 52 in practice.

  The analysis unit 15 adds the trace data 30 from t1 to t3 to the trace buffer 40. The same part initializes the loop management table 21 of level 1 at t3 and additionally writes the trace data 30 from t4 to t9 to the analysis buffer 50 of level 1. The same part adds the trace data 30 from t4 to t9 to the pattern table 52 as section data at t10. FIG. 9 is an example (1) of the pattern table 52 created by the analysis unit 15 by inputting the example (1) of the trace data 30 of FIG. The pattern ID 54 is obtained by adding P1 to the loop identifier (L1).

  The same section adds the trace data 30 from t10 to t15 to the analysis buffer 50. At t16, the same part detects the coincidence between the latest section data (t10 to t15) and the section data (t4 to t9) registered in the pattern table 52. The same unit operates the buffer pointer 51 to discard the trace data 30 from t11 to t15. Finally, the same part adds the trace data 30 at t16 to the analysis buffer 50, adds the contents of the analysis buffer 50 to the trace buffer 40, and ends the process. FIG. 10 shows an example (1) of the trace buffer 40 created by the analysis unit 15 by inputting the example (1) of the trace data 30 of FIG.

  FIG. 11 shows a source code example (2) of the traced processing program 24. FIG. 12 shows an example (2) of the trace data 30 generated when the processor 13 executes the example (2) of the trace processing program 24 shown in FIG. Assume that the variable N in the program is 3.

  The analysis unit 15 adds the trace data 30 of t1 to the trace buffer 40. The same unit initializes the loop management table 21 of level 1 at t1, and additionally writes the trace data 30 from t2 to t7 to the analysis buffer 50 of level 1. The same section adds the trace data 30 from t2 to t7 to the pattern table 52 as section data at t8. Further, the same unit stores t8 to t10 in the analysis buffer 50, and adds the trace data 30 from t8 to t10 to the pattern table 52 as section data at t11 and additionally writes it. FIG. 13 is an example (2) of the pattern table 52 created by the analysis unit 15 by inputting the example (2) of the trace data 30 of FIG. The pattern ID 54 is obtained by adding P1 and P2 to the loop identifier (L1).

  The same section adds the trace data 30 from t11 to t13 to the analysis buffer 50. At t14, the same unit detects a match between the latest section data (t11 to t13) and the section data (t8 to t10) registered in the pattern table 52. The same unit operates the buffer pointer 51 to discard the trace data 30 at t12 and t13. Finally, the same part additionally writes the trace data 30 at t14, adds the contents of the analysis buffer 50 to the trace buffer 40, and ends the process. FIG. 14 shows an example (2) of the trace buffer 40 created by the analysis unit 15 by inputting the example (2) of the trace data 30 of FIG.

  FIG. 15 shows a source code example (3) of the traced program 24. FIG. 16 shows an example (3) of the trace data 30 generated when the processor 13 executes the example (3) of the trace processing program 24 shown in FIG. Assume that the variable N in the program is 3. FIG. 17 is an example (3) of the pattern table 52 created by the analysis unit 15 by inputting the example (3) of the trace data 30 of FIG. FIG. 18 shows an example (3) of the trace buffer 40 created by the analysis unit 15 by inputting the example (3) of the trace data 30 of FIG.

  FIG. 19 shows a source code example (4) of the traced program 24. This program has a nested loop. FIG. 20 shows an example (4) of the trace data 30 generated when the processor 13 executes the example (4) of the trace processing program 24 shown in FIG. It is assumed that variables M and N in the program are 2.

  The analysis unit 15 adds the trace data 30 of t1 to the trace buffer 40. The same unit initializes the loop management table 21 of level 1 at t1, and additionally writes the trace data 30 of t2 and t3 to the analysis buffer 50 of level 1. The same part initializes the loop management table 21 of level 2 at t3 and adds the trace data 30 of t4 to t6 to the analysis buffer 50 of level 2. The same part adds the trace data 30 from t4 to t6 to the pattern table 52 of level 2 as section data at t7. FIG. 21 is an example (4-1) of the level 2 pattern table 52 created by the analysis unit 15 by inputting the example (4) of the trace data 30 of FIG. The pattern ID 54 is obtained by adding P1 to the loop identifier (L2).

  The same section adds the trace data 30 from t7 to t9 to the analysis buffer 50. At t10, the same unit detects a match between the latest section data (t7 to t9) and the section data (t4 to t6) registered in the pattern table 52. The same unit operates the buffer pointer 51 to discard the trace data 30 at t8 and t9. Here, the same part adds the trace data 30 at t10 to the analysis buffer 50 of level 2, lowers the level (value of the level storage area 22) from 2 to 1, and changes the contents of the analysis buffer 50 of level 2 to level 1. To the analysis buffer 50. The data added here is the trace data 30 from t4 to t10. However, t8 and t9 are discarded.

  The same unit stores t11 to t13 in the level 1 analysis buffer 50 and adds the trace data 30 from t2 to t13 to the level 1 pattern table 52 as section data at t14. FIG. 22 is an example (4-2) of the level 1 pattern table 52 created by the analysis unit 15 by inputting the example (4) of the trace data 30 of FIG. The pattern ID 54 is obtained by adding P1 to the loop identifier (L1).

  The same processing is performed at t15 to t25 in the same manner as the above-described t3 to t13, and at t26, the latest section data (t14 to t25) and the section data (t2 and t13) registered in the pattern table 52 are detected. To do. The same unit operates the buffer pointer 51 to discard the trace data 30 from t15 to t25. The same part finally adds the trace data 30 at t26, stores the contents of the analysis buffer 50 in the trace buffer 40, and ends the process. FIG. 23 shows an example (4) of the trace buffer 40 created by the analysis unit 15 by inputting the example (4) of the trace data 30 of FIG.

  The trace collection apparatus 10 according to the present embodiment can acquire the trace data 30 of different sequences while preventing a large amount of the trace data 30 of the same sequence from being output in large quantities during execution of the loop in which the pattern changes. The reason is that the analysis unit 15 registers a new pattern in the loop management table 21, and at least a part of the trace data 30 of the registered pattern is not output to the trace area 23.

  Moreover, the trace collection device 10 of the present embodiment has the above-described effects even when there is a loop nest. The reason is that the loop management table 21 is provided corresponding to the level of the loop nest, and the analysis unit 15 executes pattern registration and detection corresponding to the nest level.

  FIG. 24 shows a configuration of a trace collection system 70 according to the second embodiment of the present invention. The trace collection system 70 includes a trace collection device 10 and an external generation device 71 connected to the trace collection device 10. In the present embodiment, the trace collection device 10 may not include the generation unit 14. The trace data 30 is input from the external generation device 71 to the analysis unit 15. Other points are the same as in the first embodiment.

  The external generation device 71 is a control device or the like and is realized by hardware. The external generation device 71 may include an internal storage device and an arithmetic device, and the arithmetic device may be realized by executing the trace processing program 24 stored in the storage device.

  The trace collection system 70 of this embodiment can collect the trace data 30 of the traced process outside the apparatus. This is because the trace data 30 is input from the external generation device 71.

  FIG. 25 shows the basic configuration of the present invention. The trace collection apparatus 10 according to the present invention includes a trace buffer 40 that sequentially stores trace data 30 generated by execution of a traced process, a first pattern table 62, and a memory 20 that stores a first analysis buffer 61. Is provided. The apparatus further includes an analysis unit 15 that inputs each trace data 30 (first interval data) generated by each execution of the first loop in the traced process. If the input data does not detect coincidence (pattern coincidence) with any of the first section data already stored in the first pattern table 62, the input section inputs the first Are added to the first pattern table 62 and the first analysis buffer 61. Further, when detecting the pattern match, the same unit does not store at least a part of the first section data in the first analysis buffer 61, and when detecting the end of the first loop, the contents of the first analysis buffer 61 are detected. Is output to the trace buffer 40.

FIG. 1 is a configuration diagram of a trace collection apparatus 10 according to the first embodiment of the present invention. FIG. 2 shows the configuration of the trace data 30. FIG. 3 shows a source code example (1) of the trace processing program 24. FIG. 4 is a diagram showing the configuration of the trace area 23. FIG. 5 shows the configuration of the loop management table 21. FIG. 6 is an operation flowchart of the analysis unit 15. FIG. 7 is an operation flowchart of the same pattern detection processing portion of the analysis unit 15. FIG. 8 shows an example (1) of the trace data 30 generated when the processor 13 executes the example (1) of the trace processing program 24 shown in FIG. FIG. 9 is an example (1) of the pattern table 52 created by the analysis unit 15 by inputting the example (1) of the trace data 30 of FIG. FIG. 10 shows an example (1) of the trace buffer 40 created by the analysis unit 15 by inputting the example (1) of the trace data 30 of FIG. FIG. 11 shows a source code example (2) of the traced processing program 24. FIG. 12 shows an example (2) of the trace data 30 generated when the processor 13 executes the example (2) of the trace processing program 24 shown in FIG. FIG. 13 is an example (2) of the pattern table 52 created by the analysis unit 15 by inputting the example (2) of the trace data 30 of FIG. FIG. 14 shows an example (2) of the trace buffer 40 created by the analysis unit 15 by inputting the example (2) of the trace data 30 of FIG. FIG. 15 shows a source code example (3) of the traced program 24. FIG. 16 shows an example (3) of the trace data 30 generated when the processor 13 executes the example (3) of the trace processing program 24 shown in FIG. FIG. 17 is an example (3) of the pattern table 52 created by the analysis unit 15 by inputting the example (3) of the trace data 30 of FIG. FIG. 18 shows an example (3) of the trace buffer 40 created by the analysis unit 15 by inputting the example (3) of the trace data 30 of FIG. FIG. 19 shows a source code example (4) of the traced program 24. FIG. 20 shows an example (4) of the trace data 30 generated when the processor 13 executes the example (4) of the trace processing program 24 shown in FIG. FIG. 21 is an example (4-1) of the level 2 pattern table 52 created by the analysis unit 15 by inputting the example (4) of the trace data 30 of FIG. FIG. 22 is an example (4-2) of the level 1 pattern table 52 created by the analysis unit 15 by inputting the example (4) of the trace data 30 of FIG. FIG. 23 shows an example (4) of the trace buffer 40 created by the analysis unit 15 by inputting the example (4) of the trace data 30 of FIG. FIG. 24 shows a configuration of a trace collection system 70 according to the second embodiment of the present invention. FIG. 25 shows the basic configuration of the present invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Trace collection device 11 Computer 12 Trace file 13 Processor 14 Generation part 15 Analysis part 16 Output part 20 Memory 21 Loop management table 22 Level storage area 23 Trace area 24 Trace program 25 Trace collection program 30 Trace data 31 Type 32 Additional data 33 Serial number 40 Trace buffer 41 Area pointer 50 Analysis buffer 51 Buffer pointer 52 Pattern table 53 Table pointer 54 Pattern ID
55 Pattern Data 61 First Analysis Buffer 62 First Pattern Table 63 Second Analysis Buffer 64 Second Pattern Table 70 Trace Collection System 71 External Generation Device

Claims (8)

A trace buffer for sequentially storing trace data generated by execution of the traced process; a first pattern table; a memory for storing a first analysis buffer;
First section data that is each of the trace data generated by each execution of the first loop in the traced process is input, and the first section data is already stored in the first pattern table. If the first pattern match, which is a match with any of the stored first section data, is not detected, the input first section data is added to the first pattern table and the first analysis buffer. When the first pattern match is detected, at least part of the first section data is not stored in the first analysis buffer, and when the end of the first loop is detected, the first analysis buffer is detected. A trace collection device comprising an analysis unit that outputs the contents of the trace buffer to the trace buffer, wherein the memory stores a second pattern table and a second analysis buffer;
The analysis unit inputs second interval data that is each of the trace data generated by each execution of the second loop included in the first loop, and the second interval data Does not detect a second pattern match that matches the trace data of any second section stored in the second pattern table, the second section data is stored in the second pattern table and When the second analysis buffer is additionally written and the second pattern match is detected, at least part of the second section data is not stored in the second analysis buffer, and the end of the second loop is completed. A trace collection device that outputs the contents of the second analysis buffer to the first analysis buffer when detected. With a trace file,
The trace collection device according to claim 1, further comprising an output unit that outputs the contents of the trace buffer to the trace file. A generation unit that executes the traced process, and generates the trace data of different types before and after the start of the first loop, and at the start of each iteration of the in-loop repeat process;
The analysis unit that detects the start and end of the first loop and the start and end of each execution of the first loop based on the trace data generated by the generation unit. Or 2 trace collection devices. The trace data connected to the trace collection device, executing the traced process, before and after the start of the first loop, and at the start of each repetition of the in-loop process. An external generation device for generating
The analysis unit that detects the start and end of the first loop and the start and end of each execution of the first loop based on the trace data generated by the external generation device. Or a trace collection system comprising two trace collection devices. A trace buffer for sequentially storing trace data generated by execution of the traced process, a first pattern table, a first analysis buffer, a second pattern table, and a memory for storing a second analysis buffer; Computer
First section data that is each of the trace data generated by each execution of the first loop in the traced process is input, and the first section data is already stored in the first pattern table. If the first pattern match, which is a match with any of the stored first section data, is not detected, the input first section data is added to the first pattern table and the first analysis buffer. When the first pattern match is detected, at least part of the first section data is not stored in the first analysis buffer, and when the end of the first loop is detected, the first analysis buffer is detected. A trace collection program for executing an analysis process for outputting the contents of the trace buffer to the trace buffer,
In the computer,
Second interval data that is each of the trace data generated by each execution of the second loop included in the first loop is input, and the second interval data is input to the second loop If the second pattern match, which is a match with the trace data of any second section stored in the pattern table, is not detected, the second section data is converted into the second pattern table and the second analysis. When the pattern match is detected by adding to the buffer, at least a part of the second section data is not stored in the second analysis buffer, and when the end of the second loop is detected, the second analysis is performed. A trace collection program for executing the analysis processing for outputting the contents of the buffer to the first analysis buffer. On the computer with the trace file,
The trace collection program according to claim 5, wherein an output process for outputting the contents of the trace buffer to the trace file is executed. Generation processing for executing the traced processing in the computer and generating the trace data of different types before and after the start of the first loop and at the start of each iteration of the intra-loop iteration processing. When,
The analysis processing for detecting the start and end of the first loop and the start and end of each execution of the first loop is executed based on the trace data generated by the generation unit. 5 or 6 trace collection programs. A trace buffer for sequentially storing trace data generated by execution of the traced process, a first pattern table, a first analysis buffer, a second pattern table, and a memory for storing a second analysis buffer; Computer with
First section data that is each of the trace data generated by each execution of the first loop in the traced process is input, and the first section data is already stored in the first pattern table. If the first pattern match, which is a match with any of the stored first section data, is not detected, the input first section data is added to the first pattern table and the first analysis buffer. When the first pattern match is detected, at least part of the first section data is not stored in the first analysis buffer, and when the end of the first loop is detected, the first analysis buffer is detected. A trace collection method comprising an analysis step of outputting the contents of
The computer is
Second interval data that is each of the trace data generated by each execution of the second loop included in the first loop is input, and the second interval data is input to the second loop If the second pattern match, which is a match with the trace data of any second section stored in the pattern table, is not detected, the second section data is converted into the second pattern table and the second analysis. When adding to the buffer and detecting the second pattern match, at least a part of the second section data is not stored in the second analysis buffer, and when the end of the second loop is detected, A trace collection method comprising the analysis step of outputting the contents of two analysis buffers to the first analysis buffer.

Images