WO2012077704A1 - デバッグスタブサーバ、デバッグ方法およびプログラム - Google Patents
デバッグスタブサーバ、デバッグ方法およびプログラム Download PDFInfo
- Publication number
- WO2012077704A1 WO2012077704A1 PCT/JP2011/078272 JP2011078272W WO2012077704A1 WO 2012077704 A1 WO2012077704 A1 WO 2012077704A1 JP 2011078272 W JP2011078272 W JP 2011078272W WO 2012077704 A1 WO2012077704 A1 WO 2012077704A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- debug
- program
- control
- control instructions
- control instruction
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2268—Logging of test results
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
Definitions
- the present invention is based on the priority claim of Japanese patent application: Japanese Patent Application No. 2010-272840 (filed on Dec. 07, 2010), the entire contents of which are incorporated herein by reference. Shall.
- the present invention relates to a debug stub server, a debugging method, and a program, and more particularly to a debug stub server, a debugging method, and a program that realize debugging from a plurality of information terminals.
- Non-patent document 1, Non-patent document 2, Patent document 1, and Patent document 2 describe a debug system.
- FIG. 10 is a block diagram schematically showing the configuration of the debug system described in these documents.
- the debug system includes a debug target device 210 and an information terminal 220 used by a worker who performs debugging, and the debug target device 210 and the information terminal 220 are configured to be in a one-to-one relationship. ing.
- the debug system may include a plurality of devices to be debugged 210, or may include a plurality of processes.
- one debugging target device 210 and one information terminal 220 are in a one-to-one relationship, display the internal state of the debugging target device 210, and stop program execution in the debugging target device 210. And a screen that enables resumption control. According to such a debug system, it is possible to detect an error in a program or to detect an error in a hardware and repair the error while displaying the internal state of the debug target device 210 based on these controls.
- Non-Patent Document 1 the debug target device 210 and the information terminal 220 are mounted on the same computer.
- the debug function is present on the debug target apparatus 210, and a debug operation is performed remotely from an externally connected information terminal 220. At this time, the debug function is built in the server on the debug target device 210, and it is not possible to execute a debug function other than the pre-built function.
- FIG. 11 is a block diagram showing the configuration of the debug system described in Patent Document 1.
- This debug system is a test apparatus for a plurality of JTAG (Joint Test Action Group) compliant integrated circuits and a test system for testing a plurality of integrated circuits.
- JTAG Joint Test Action Group
- each integrated circuit including an on-chip debug protocol is provided with a master controller 102 operable to execute the corresponding test protocol, and the master controller 102 instructs the integrated circuit according to the configuration data.
- a programmable switch (not shown) that selectively forms a test loop is provided between the master controller 102 and a selected one of the integrated circuits, the test loop being selected from among the test protocols.
- a data bus is provided that connects the master controller 102 to each of the integrated circuits.
- the method and operation unit for adjusting the control device of Patent Document 2 similarly handle a plurality of integrated circuits or processes.
- a plurality of processes are buffered using a memory, and information on the plurality of processes is provided to the outside by reading the buffer serially.
- Patent Document 3 when debugging a program using an inter-task sharing routine at the same time, for example, an online program using an inter-task sharing routine, etc. A debug processing apparatus that enables debugging in an independent environment is described.
- JP 2000-148528 A JP 2010-173633 A JP-A-6-103105
- the debug status cannot be monitored from a plurality of information terminals. Moreover, when control from a plurality of information terminals competes, debugging cannot proceed without contradiction.
- debug information cannot be displayed simultaneously on a plurality of information terminals. This is because the debugging system described above assumes debugging with a single information terminal.
- debug control cannot be performed simultaneously from a plurality of information terminals, and there is a risk that contradiction may occur or an uncontrollable state may occur due to control from a plurality of information terminals. is there.
- the debug processing device described in Patent Document 3 arbitrates instructions received from a plurality of information terminals and provides an independent debugging environment for each of the plurality of information terminals. That is, according to the debug processing apparatus described in Patent Document 3, a separate debug result is output to each information terminal in accordance with an instruction received from each information terminal. At this time, the debug result cannot be shared among a plurality of information terminals, and the other information terminal cannot grasp the debug result based on the instruction of one information terminal.
- An object of the present invention is to provide a debug stub server, a debugging method, and a program for solving such a problem.
- the debug stub server is: A plurality of control instructions for a debug program are received from a plurality of information terminals, and by arbitrating the plurality of control instructions, a simultaneously executable one of the plurality of control instructions is selected and transferred to the debug program The mediation department; A transfer unit configured to transfer a debug result acquired by the debug program to the plurality of information terminals according to the control instruction selected by the arbitration unit.
- the debugging method is: A step in which a debug stub server receives a plurality of control instructions for a debug program from a plurality of information terminals; Selecting a simultaneously executable one of the plurality of control instructions by arbitrating the plurality of control instructions; Transferring the selected control instructions to the debug program; Transferring a debug result acquired by the debug program in response to the selected control instruction to the plurality of information terminals.
- the program according to the third aspect of the present invention is: Receiving a plurality of control instructions for a debug program from a plurality of information terminals; Processing to select simultaneously executable ones of the plurality of control instructions by arbitrating the plurality of control instructions; A process of transferring the selected control instruction to the debug program; And causing the computer to execute a process of transferring a debug result acquired by the debug program to the plurality of information terminals in accordance with the selected control instruction.
- the debug result obtained by the debug program is shared among the plurality of information terminals according to the control instruction issued independently from the plurality of information terminals. be able to.
- FIG. 1 It is a block diagram which shows the structure of the debug controller in the information terminal in an Example as an example. It is a block diagram which shows the structure of the debug screen in the information terminal in an Example as an example. It is a block diagram which shows the structure of the debug stub server in an Example as an example. It is a block diagram which shows the structure of a debug system as an example. It is a block diagram which shows the structure of the test apparatus described in patent document 1. FIG.
- the debug stub server (11) has a control mechanism for enabling debugging by a plurality of information terminals (20a to 20c).
- the debug stub server (11) is provided between the debug target device (10) that executes the debug program and the plurality of information terminals (20a to 20c). Further, the debug stub server (11) and the information terminals (20a to 20c) are connected via a network such as TCP-IP, USB, or serial.
- debugging by a plurality of information terminals is realized by separating the debug stub server (11) close to the debug target device (10) and the information terminals (20a to 20c).
- the debug stub server (11) controls setting of breakpoints, step execution, etc., and analysis instruction of performance quality information such as profile and coverage collection for the debug program executed in the debug target device (10). Handle the display of results in a batch.
- the debug stub server (11) includes an arbitration unit (16) and a transfer unit (18).
- the arbitration unit (16) receives a plurality of control instructions for the debug program from a plurality of information terminals, and selects a controllable one of the plurality of control instructions by arbitrating the plurality of control instructions.
- a transfer part (18) transfers the debug result acquired by the debug program to a some information terminal according to the control instruction
- the arbitration unit (16) preferably notifies the information terminal that has transmitted the control instruction not selected by the arbitration among the plurality of control instructions that the control instruction has not been selected.
- the arbitration unit (16) may arbitrate the received plurality of control instructions with reference to a control condition library that holds a rule for arbitrating a plurality of control instructions for the debug program. Further, the arbitrating unit (16) sets a plurality of control instructions for the debug program to at least one of the priority of the control instructions, the number assigned to the information terminal that has transmitted the control instructions, and the order in which the control instructions are received. Mediation may be performed accordingly.
- the debug result obtained by the debug program can be shared among the plurality of information terminals in accordance with the control instructions issued independently from the plurality of information terminals. This is because the debug stub server transfers a plurality of control instructions received from a plurality of information terminals simultaneously executable to the debug program, and a debug result obtained by the debug program according to the control instructions executable simultaneously Is transmitted to a plurality of information terminals.
- debug information can be supplied to a plurality of information terminals. This is because the debug stub server collects debug information and then provides information to the information terminal.
- debug control can be performed simultaneously from a plurality of information terminals. This is because the debug stub server performs exclusive control based on the control condition library.
- the debug screen in each information terminal can be freely configured. This is because the debug terminal can transfer the debug screen only, not the debug screen, so that the information terminal can freely configure the debug screen.
- the arbitration unit notifies an information terminal that has transmitted a control instruction that is not selected by arbitration among the plurality of control instructions, that the control instruction has not been selected.
- the arbitration unit may arbitrate a plurality of received control instructions with reference to a control condition library that holds a rule for arbitrating a plurality of control instructions for the debug program.
- the arbitration unit arbitrates a plurality of control instructions for the debug program according to at least one of a priority of the control instruction, a number assigned to the information terminal that has transmitted the control instruction, and an order of receiving the control instruction. You may make it do.
- the debug system is configured to send the control instruction for the debug stub server and the debug program received from the user to the debug stub server, and to display the debug result transferred from the debug stub server.
- a plurality of information terminals may be provided in either a debug target device that executes the debug program or the plurality of information terminals.
- Each of the plurality of information terminals includes a display method library that holds a display method of debug results; It is preferable to include a display designating unit that displays the debug result according to a display method stored in the display method library.
- the debugging method according to the second aspect is as described above.
- the debug stub server arbitrates a plurality of received control instructions with reference to a control condition library that holds a rule for arbitrating a plurality of control instructions for the debug program. Also good.
- the debug stub server receives a plurality of control instructions for the debug program, the priority of the control instructions, the number assigned to the information terminal that sent the control instructions, and the order in which the control instructions are received Arbitration may be performed according to at least one of the above.
- the program is related to the third viewpoint. This program can be stored on a non-transient computer-readable recording medium and can be embodied as a storage state.
- the information terminal that has transmitted a control instruction that is not selected by arbitration among the plurality of control instructions may cause a computer to execute a process of notifying that the control instruction has not been selected. preferable.
- the received plurality of control instructions may be arbitrated with reference to a control condition library that holds a rule for arbitrating a plurality of control instructions for the debug program.
- the plurality of control instructions for the debug program are in accordance with at least one of the priority of the control instruction, the number assigned to the information terminal that has transmitted the control instruction, and the order in which the control instruction is received. May be used for mediation.
- FIG. 2 is a block diagram showing the configuration of the debug system according to the present embodiment.
- the debug system includes a debug target device 10 that is a device to be verified, and a plurality of information terminals 20a to 20c.
- the number of information terminals is three as an example, but the number of information terminals is not limited to this.
- the debug target device 10 includes a debug stub server 11, a verification target system 12, and a control condition library 14.
- the program execution unit 13 is activated separately from the debug stub server 11 in the verification target system 12.
- the information terminals 20a to 20c include debug controllers 31a to 31c and debug screens 32a to 32c, respectively.
- the debug system includes a debug program 71 and debug execution data 72.
- the debug stub server 11 is connected to the debug controllers 31a to 31c of the information terminals 20a to 20c by Ethernet, USB, serial communication or the like.
- the debug stub server 11 receives a debug program and data from a program execution unit 13 that debugs and analyzes the verification target system 12, and debugs or analyzes the debug program and data based on instructions from the information terminals 20a to 20c. I do.
- the debug stub server 11 sends the results of debugging or analysis to the debug screens 32a to 32c of the information terminals 20a to 20c via the debug controllers 31a to 31c.
- the debug stub server 11 When the debug stub server 11 receives control instructions such as stop, step, and information acquisition from the debug controllers 31a to 31c, according to the control conditions described in the control condition library 14, Control is performed by determining an executable control instruction.
- the debug stub server 11 notifies the debug screens 32a to 32c of the control instructions that cannot be executed via the debug controllers 31a to 31c.
- the program execution unit 13 activates a debugging analysis program such as a debugger, coverage acquisition, automatic test, memory management, profile acquisition, and the like.
- the program execution unit 13 operates based on an instruction from the debug stub server 11 and returns a result to the debug stub server 11.
- the debug controllers 31 a to 31 c generate the debug program 71 and the debug execution data 72 and transfer them to the debug stub server 11.
- the debug controllers 31a to 31c control the start, end, stop, display instruction, designation of the stop position, and the like of debugging, and display on the debug screens 32a to 32c.
- the debug screens 32a to 32c display debug information received from the debug stub server 11 via the debug controllers 31a to 31c, a button for a debug instruction, a command input screen, source code, and a stop location in the source code. Display so that can be specified.
- the control condition library 14 holds arbitration rules when a plurality of instructions that cannot be executed simultaneously are received, such as when a similar instruction is simultaneously received from a plurality of information terminals 20a to 20c.
- the debug stub server 11 refers to the control condition library 14 and performs exclusive control for a plurality of instructions.
- the debug program 71 and the debug execution data 72 are a program compiled for the verification target system and execution data for the purpose of execution and debugging in the debug target device 10, respectively.
- FIGS. 3 and 4 are flowcharts showing an example of the operation of the debug system according to this embodiment. With reference to FIGS. 2 to 4, the operation of the entire debugging system of this embodiment will be described.
- a debug program 71 that can be executed by the verification target system 12 of the debug target device 10 in the information terminals 20a to 20c or another system
- a debug program for knowing the internal state or a debug program for analysis is used.
- Generate step S11). These debug programs are generated by setting a compile option or by executing another program during or after compilation.
- debug execution data 72 is prepared as data for debugging or analysis (step S12).
- Step S31 the debug controllers 31a to 31c are activated, and the debug screens 32a to 32c are activated.
- the debug stub server 11 is activated on the debug target device 10, and the connection between the debug stub server 11 and the debug controllers 31a to 31c is established by communication means such as Ethernet, USB, PCI, and serial (step S32).
- step S32 Using the network established in step S32, the debug program 71 and the debug execution data 72 prepared in steps S11 and S12 are transferred to the program execution unit 13 via the debug stub server 11 (step S13). .
- An instruction to start the debug program 71 is output from any of the debug controllers 31a to 31c (step S14), and the debug program 71 is started (step S15).
- an instruction to specify the stop position of the program or change the amount of the type of acquired information is instructed on the debug screens 32a to 32c and is output from the debug controllers 31a to 31c (step S16-1, S16-2).
- the debug stub server 11 inquires the control condition library 14 in which the control conditions are set in advance, executes the control that matches the control conditions, and controls that are not executed via the debug controllers 31a to 31c that are the control designation sources. This is displayed on the debug screens 32a to 32c (step S17).
- step S18 data is input from the program execution unit 13 to the debug program 71 and executed (step S18), and a debug result is acquired and transferred (step S19).
- step S19 The result obtained in step S19 is displayed on the debug screens 32a to 32c by the display method specified by the debug controllers 31a to 31c via the program execution unit 13, the debug stub server 11, and the debug controllers 31a to 31c. (Step S20).
- step S21 an end instruction is output from the debug screens 32a to 32c (step S21).
- the termination instruction arrives at the debug stub server 11, the debugging is terminated (step S22).
- a debug program 71 that can be executed by the verification target system 12 of the debug target device 10 in the information terminals 20a to 20c or another system
- a debug program for knowing the internal state or a debug program for analysis is used.
- Generate step S41.
- These debug programs are generated by setting a compile option or by executing another program during or after compilation.
- debug execution data 72 is prepared as data for debugging or analysis (step S42).
- the debug controllers 31a to 31c are activated and the debug screens 32a to 32c are activated (step S61).
- the debug stub server 11 is activated on the debug target device 10, and the connection between the debug stub server 11 and the debug controllers 31a to 31c is established by communication means such as Ethernet, USB, PCI, and serial (step S62).
- step S62 Using the network established in step S62, the debug program 71 and the debug execution data 72 prepared in steps S41 and S42 are transferred to the program execution unit 13 via the debug stub server 11 (step S43). .
- the debug stub server 11 inquires about the control conditions stored in the control condition library 14 and sets the execution conditions. As for the control that is not executed, the fact is displayed on the debug screens 32a to 32c via the debug controllers 31a to 31c as the control designation source (step S45).
- step S46 The activation of the executable debug program 71 with control is instructed (step S46), and the debug program 71 is activated (step S47).
- Step S48 Data is input from the program execution unit 13 to the debug program 71, and the debug program 71 is executed (step S48).
- step S48 The result acquired in step S48 is displayed on the debug screens 32a to 32c by the display method specified by the debug controllers 31a to 31c via the program execution unit 13, the debug stub server 14, and the debug controllers 31a to 31c. (Step S49).
- step S50 When the end instruction is output from the debug screens 32a to 32c and the output end instruction arrives at the debug stub server 11, the debugging is ended (step S50).
- FIG. 5 is a block diagram showing the configuration of the debug system according to the present embodiment.
- the debug system includes a debug target device 10 that is a device to be verified, and a plurality of information terminals 20a to 20c.
- the number of information terminals is three as an example, but the number of information terminals is not limited to this.
- the debug stub server 11 is provided on the debug target device 10 (FIG. 2).
- the debug stub server 11 is provided on the information terminal 20a. Since the operation of each unit illustrated in FIG. 5 is the same as the operation of each unit in the first embodiment, the description thereof is omitted.
- the debug stub server 11 may be provided on any one of the information terminals 20a to 20c. Further, if the debug system has some communication means between the debug stub server 11 and the program execution unit 13, the debug stub is provided on a separate device other than the debug target device 10 and the information terminals 20a to 20c. A server 11 may be provided. According to the debug system of this embodiment, the same operation as that of the debug system according to the first embodiment can be realized.
- the number of information terminals is three, but the number of information terminals can be expanded to an arbitrary number.
- the debug stub server 11 and the program execution unit 13 are independent.
- the debug stub server 11 is connected to the debug controllers 31a to 31c of the plurality of information terminals 20a to 20c via a network. Further, the debug stub server 11 executes and controls debugging, transfers results, and communicates with the debug controllers 31a to 31c. Thereby, debugging by the plurality of information terminals 20a to 20c is realized.
- the debug target device 10 is debugged from the three information terminals 20a to 20c.
- the debug target device 10 and the information terminals 20a to 20c are physically connected by Ethernet, USB, PCI, PCI Express, serial, or the like. Therefore, data can be exchanged between the debug target apparatus 10 and the information terminals 20a to 20c.
- compilation is performed by the command CC using the “-g” command that enables debugging by the UNIX Cx dbx command to prepare an executable debug program (step of FIG. 3). S11).
- commands such as profile acquisition, coverage acquisition, automatic test, and memory management status investigation can be executed.
- test data for debugging and debug data are prepared (step S12). These data may be generated by the information terminals 20a to 20c or the debug target device 10, or may be generated by other devices.
- the debug controllers 31a to 31c and the debug screens 32a to 32c are activated on the information terminals 20a to 20c (step S31). Further, the debug stub server 11 is activated on the debug target device 10 (step S32). When the debug screens 32a to 32c are activated, the debug controllers 31a to 31c may be activated simultaneously.
- an instruction to start the debug program 71 is output from the debug screen 32a of one information terminal 20a among the plurality of information terminals 20a to 20c (step S14).
- step S15 When the program execution unit 13 receives a start instruction via the debug controller 31a and the debug stub server 11, the program execution unit 13 starts the debug program 71 (step S15).
- the debug stub server 11 when there are a plurality of control designations when the debug program 71 is activated, the debug stub server 11 performs exclusive control determination, designates only the controls that can be performed simultaneously as options, and displays other controls as debug screens. An error is displayed on 32a to 32c (step S45 in FIG. 4).
- the debug stub server 11 when there are a plurality of control designations when the debug program 71 is operated, the debug stub server 11 performs exclusive control determination and only controls that can be performed simultaneously. Is designated as an option, and other controls are displayed as errors on the debug screens 32a to 32c (step S17 in FIG. 3).
- step S18 the debug program 71 with control repeats control such as stop and restart, for example, the debug is continued until the debug is completed, and the debug results are displayed on the debug screens 32a to 32c (step S18).
- step S20 While adding or deleting control, debugging is repeated until an instruction to end debugging (step S21) is given.
- FIG. 6 is a flowchart showing a method for determining the control exclusivity by the debug stub server 11. Referring to FIG. 6, the debug stub server 11 accepts all controls at once (step S71).
- the debug stub server 11 determines a controllable process and its order using the control exclusivity described in the control condition library 14 or the priority of the process (step S72).
- control condition library 14 the priority of processing such as the first-come-first-served basis of control, the priority of the information terminal, the priority of control, and the like is made into a library.
- the control condition library 14 may be placed in any location that can be referred to from the debug stub server 11. As shown in FIG. 2, the control condition library 14 may be provided on the debug target apparatus 10.
- control condition library 14 detection of exclusive control, determination of control when there is exclusive, and processing order of exclusive control are set by a predetermined method. For example, there is an exclusivity between stop and restart, but it is determined whether to perform stop or restart control by a preset method such as the arrival order of these controls or the order of numbers assigned to the information terminals. Is done.
- FIG. 7 is a block diagram showing the configuration of the debug controller 31a in the information terminal 20a.
- the debug controller 31a includes a network interface 41 responsible for communication with the debug stub server 11, a control condition transfer unit 42 that transfers control conditions, a control error reception unit 43 that receives control errors, an execution start unit 44, A result receiving unit 45 for receiving a debug result and an end instruction unit 46 are provided.
- FIG. 8 is a block diagram showing a configuration other than the configuration shown in FIG. 7 in the configuration of the information terminal 20a.
- the information terminal 20 a further includes a display method library 56.
- the debug screen 32a includes a startup control unit 51, an operation control unit 52, a display specification unit 53 for specifying a display method, a result display unit 54 for displaying a debug result, and a control error display unit for displaying a control error. 55.
- the display method library 56 sets a display method.
- the display method library 56 and the display designating unit 53 make it possible, for example, to hide or display the display of a certain register and to switch the layout and size of the screen for each debug screen.
- FIG. 9 is a block diagram showing the configuration of the debug stub server 11.
- the debug stub server 11 includes an external network interface 61 that communicates with the information terminal 20a, an execution control unit 62, a transfer unit 63 that transfers data, programs, and results, and a verification target system 12.
- the verification target interface 64 that performs communication of the above and the arbitration unit 65 that determines the control order based on the information from the control condition library 14 are provided.
- the debug system according to the present invention can be applied to verification, debugging, quality analysis, performance analysis, etc. of LSIs for embedded systems, computers, microprocessors, digital home appliances or mobile phones.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
Description
本発明は、日本国特許出願:特願2010-272840号(2010年12月07日出願)の優先権主張に基づくものであり、同出願の全記載内容は引用をもって本書に組み込み記載されているものとする。
本発明は、デバッグスタブサーバ、デバッグ方法およびプログラムに関し、特に、複数の情報端末からのデバッグを実現するデバッグスタブサーバ、デバッグ方法およびプログラムに関する。
デバッグプログラムに対する複数の制御指示を複数の情報端末から受けるとともに、該複数の制御指示を調停することにより、該複数の制御指示のうちの同時に実行可能なものを選択して該デバッグプログラムに転送する調停部と、
前記調停部により選択された制御指示に応じて前記デバッグプログラムによって取得されたデバッグ結果を、前記複数の情報端末に転送する転送部と、を備えている。
デバッグスタブサーバが、デバッグプログラムに対する複数の制御指示を複数の情報端末から受ける工程と、
前記複数の制御指示を調停することにより、前記複数の制御指示のうちの同時に実行可能なものを選択する工程と、
前記選択された制御指示を前記デバッグプログラムに転送する工程と、
前記選択された制御指示に応じて前記デバッグプログラムによって取得されたデバッグ結果を、前記複数の情報端末に転送する工程と、を含む。
デバッグプログラムに対する複数の制御指示を複数の情報端末から受ける処理と、
前記複数の制御指示を調停することにより、前記複数の制御指示のうちの同時に実行可能なものを選択する処理と、
前記選択された制御指示を前記デバッグプログラムに転送する処理と、
前記選択された制御指示に応じて前記デバッグプログラムによって取得されたデバッグ結果を、前記複数の情報端末に転送する処理と、をコンピュータに実行させる。
[形態1]
上記第1の視点に係るデバッグスタブサーバのとおりである。
[形態2]
前記調停部は、前記複数の制御指示のうちの調停によって選択されなかった制御指示を送出した情報端末に、該制御指示が選択されなかった旨を通知することが好ましい。
[形態3]
前記調停部は、前記デバッグプログラムに対する複数の制御指示を調停するためのルールを保持する制御条件ライブラリを参照して、受信した複数の制御指示を調停するようにしてもよい。
[形態4]
前記調停部は、前記デバッグプログラムに対する複数の制御指示を、制御指示の優先度、制御指示を送出した情報端末に付された番号、および、制御指示を受信した順序の少なくともいずれかに応じて調停するようにしてもよい。
[形態5]
デバッグシステムは、上記のデバッグスタブサーバと、利用者から受けた前記デバッグプログラムに対する制御指示を前記デバッグスタブサーバに送出するとともに、前記デバッグスタブサーバから転送されたデバッグ結果を表示するように、それぞれ構成された複数の情報端末と、を備えていることが好ましい。
[形態6]
前記デバッグスタブサーバは、前記デバッグプログラムを実行するデバッグ対象装置、または、前記複数の情報端末のうちのいずれかに設けられていてもよい。
[形態7]
前記複数の情報端末は、それぞれ、デバッグ結果の表示方法を保持する表示方式ライブラリと、
前記表示方式ライブラリに格納された表示方法に応じて前記デバッグ結果を表示する表示指定部と、を備えていることが好ましい。
[形態8]
上記第2の視点に係るデバッグ方法のとおりである。
[形態9]
上記形態に係るデバッグ方法において、デバッグスタブサーバが、前記複数の制御指示のうちの調停によって選択されなかった制御指示を送出した情報端末に、該制御指示が選択されなかった旨を通知する工程を含むことが好ましい。
[形態10]
上記形態に係るデバッグ方法において、デバッグスタブサーバが、前記デバッグプログラムに対する複数の制御指示を調停するためのルールを保持する制御条件ライブラリを参照して、受信した複数の制御指示を調停するようにしてもよい。
[形態11]
上記形態に係るデバッグ方法において、デバッグスタブサーバが、前記デバッグプログラムに対する複数の制御指示を、制御指示の優先度、制御指示を送出した情報端末に付された番号、および、制御指示を受信した順序の少なくともいずれかに応じて調停するようにしてもよい。
[形態12]
上記第3の視点に係るプログラムのとおりである。このプログラムは、ノントランジエントなコンピュータ読み取り可能な(non-transient computer-readable)記録媒体に記憶することができ、かつ、記憶状態のものとして具体化されることができる。
[形態13]
上記形態に係るプログラムにおいて、前記複数の制御指示のうちの調停によって選択されなかった制御指示を送出した情報端末に、該制御指示が選択されなかった旨を通知する処理をコンピュータに実行させることが好ましい。
[形態14]
上記形態に係るプログラムにおいて、前記デバッグプログラムに対する複数の制御指示を調停するためのルールを保持する制御条件ライブラリを参照して、受信した複数の制御指示を調停するようにしてもよい。
[形態15]
上記形態に係るプログラムにおいて、前記デバッグプログラムに対する複数の制御指示を、制御指示の優先度、制御指示を送出した情報端末に付された番号、および、制御指示を受信した順序の少なくともいずれかに応じて調停するようにしてもよい。
第1の実施形態に係るデバッグシステムについて、図面を参照して説明する。
第2の実施形態に係るデバッグシステムについて、図面を参照して説明する。
11 デバッグスタブサーバ
12 検証ターゲットシステム
13 プログラム実行部
14 制御条件ライブラリ
16 調停部
18 転送部
20a~20c 情報端末
31a~31c デバッグコントローラ
32a~32c デバッグ画面
41 ネットワークインタフェース
42 制御条件転送部
43 制御エラー受け取り部
44 実行開始部
45 結果受け取り部
46 終了指示部
51 起動時制御部
52 動作時制御部
53 表示指定部
54 結果表示部
55 制御エラー表示部
56 表示方式ライブラリ
61 外部ネットワークインタフェース
62 実行制御部
63 転送部
64 検証ターゲットインタフェース
65 調停部
71 デバッグプログラム
72 デバッグ実行用データ
100 テストアーキテクチャ
102 マスタコントローラ
104 スレイブJTAGターゲット
106,108 JTAGコネクタ
110 直列レジスタチェーン
120~124 境界相互接続
210 デバッグ対象装置
220 情報端末
IC112~IC118 集積回路
Claims (15)
- デバッグプログラムに対する複数の制御指示を複数の情報端末から受けるとともに、該複数の制御指示を調停することにより、該複数の制御指示のうちの同時に実行可能なものを選択して該デバッグプログラムに転送する調停部と、
前記調停部により選択された制御指示に応じて前記デバッグプログラムによって取得されたデバッグ結果を、前記複数の情報端末に転送する転送部と、を備えていることを特徴とするデバッグスタブサーバ。 - 前記調停部は、前記複数の制御指示のうちの調停によって選択されなかった制御指示を送出した情報端末に、該制御指示が選択されなかった旨を通知することを特徴とする、請求項1に記載のデバッグスタブサーバ。
- 前記調停部は、前記デバッグプログラムに対する複数の制御指示を調停するためのルールを保持する制御条件ライブラリを参照して、受信した複数の制御指示を調停することを特徴とする、請求項1または2に記載のデバッグスタブサーバ。
- 前記調停部は、前記デバッグプログラムに対する複数の制御指示を、制御指示の優先度、制御指示を送出した情報端末に付された番号、および、制御指示を受信した順序の少なくともいずれかに応じて調停することを特徴とする、請求項1ないし3のいずれか1項に記載のデバッグスタブサーバ。
- 請求項1ないし4のいずれか1項に記載のデバッグスタブサーバと、
利用者から受けた前記デバッグプログラムに対する制御指示を前記デバッグスタブサーバに送出するとともに、前記デバッグスタブサーバから転送されたデバッグ結果を表示するように、それぞれ構成された複数の情報端末と、を備えていることを特徴とするデバッグシステム。 - 前記デバッグスタブサーバは、前記デバッグプログラムを実行するデバッグ対象装置または前記複数の情報端末のうちのいずれかに設けられていることを特徴とする、請求項5に記載のデバッグシステム。
- 前記複数の情報端末は、それぞれ、デバッグ結果の表示方法を保持する表示方式ライブラリと、
前記表示方式ライブラリに格納された表示方法に応じて前記デバッグ結果を表示する表示指定部と、を備えていることを特徴とする、請求項5または6に記載のデバッグシステム。 - デバッグスタブサーバが、デバッグプログラムに対する複数の制御指示を複数の情報端末から受ける工程と、
前記複数の制御指示を調停することにより、前記複数の制御指示のうちの同時に実行可能なものを選択する工程と、
前記選択された制御指示を前記デバッグプログラムに転送する工程と、
前記選択された制御指示に応じて前記デバッグプログラムによって取得されたデバッグ結果を、前記複数の情報端末に転送する工程と、を含むことを特徴とするデバッグ方法。 - 前記デバッグスタブサーバが、前記複数の制御指示のうちの調停によって選択されなかった制御指示を送出した情報端末に、該制御指示が選択されなかった旨を通知する工程を含むことを特徴とする、請求項8に記載のデバッグ方法。
- 前記デバッグスタブサーバが、前記デバッグプログラムに対する複数の制御指示を調停するためのルールを保持する制御条件ライブラリを参照して、受信した複数の制御指示を調停することを特徴とする、請求項8または9に記載のデバッグ方法。
- 前記デバッグスタブサーバが、前記デバッグプログラムに対する複数の制御指示を、制御指示の優先度、制御指示を送出した情報端末に付された番号、および、制御指示を受信した順序の少なくともいずれかに応じて調停することを特徴とする、請求項8ないし10のいずれか1項に記載のデバッグ方法。
- デバッグプログラムに対する複数の制御指示を複数の情報端末から受ける処理と、
前記複数の制御指示を調停することにより、前記複数の制御指示のうちの同時に実行可能なものを選択する処理と、
前記選択された制御指示を前記デバッグプログラムに転送する処理と、
前記選択された制御指示に応じて前記デバッグプログラムによって取得されたデバッグ結果を、前記複数の情報端末に転送する処理とを、コンピュータに実行させることを特徴とするプログラム。 - 前記複数の制御指示のうちの調停によって選択されなかった制御指示を送出した情報端末に、該制御指示が選択されなかった旨を通知する処理を、コンピュータに実行させることを特徴とする、請求項12に記載のプログラム。
- 前記デバッグプログラムに対する複数の制御指示を調停するためのルールを保持する制御条件ライブラリを参照して、受信した複数の制御指示を調停する処理を、コンピュータに実行させることを特徴とする、請求項12または13に記載のプログラム。
- 前記デバッグプログラムに対する複数の制御指示を、制御指示の優先度、制御指示を送出した情報端末に付された番号、および、制御指示を受信した順序の少なくともいずれかに応じて調停する処理を、コンピュータに実行させることを特徴とする、請求項12ないし14のいずれか1項に記載のプログラム。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2012547887A JPWO2012077704A1 (ja) | 2010-12-07 | 2011-12-07 | デバッグスタブサーバ、デバッグ方法およびプログラム |
US13/992,539 US9292395B2 (en) | 2010-12-07 | 2011-12-07 | Debug stub server, debug method, and program |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2010-272840 | 2010-12-07 | ||
JP2010272840 | 2010-12-07 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012077704A1 true WO2012077704A1 (ja) | 2012-06-14 |
Family
ID=46207191
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2011/078272 WO2012077704A1 (ja) | 2010-12-07 | 2011-12-07 | デバッグスタブサーバ、デバッグ方法およびプログラム |
Country Status (3)
Country | Link |
---|---|
US (1) | US9292395B2 (ja) |
JP (1) | JPWO2012077704A1 (ja) |
WO (1) | WO2012077704A1 (ja) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113068250A (zh) * | 2021-04-01 | 2021-07-02 | 广东电网有限责任公司清远供电局 | 一种时间同步装置、方法、设备及存储介质 |
US20210263817A1 (en) * | 2020-11-09 | 2021-08-26 | Beijing Baidu Netcom Science And Technology Co., Ltd. | Method and apparatus for sending debugging instruction |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014120200A1 (en) * | 2013-01-31 | 2014-08-07 | Hewlett-Packard Development Company, L.P. | Methods and apparatus for debugging of remote systems |
US9552279B2 (en) * | 2013-08-16 | 2017-01-24 | Nxp Usa, Inc. | Data bus network interface module and method therefor |
US10223241B2 (en) * | 2017-03-02 | 2019-03-05 | International Business Machines Corporation | Resuming a remote debugging session using a backup node |
US10895597B2 (en) * | 2018-11-21 | 2021-01-19 | Advanced Micro Devices, Inc. | Secure coprocessor assisted hardware debugging |
US11972240B2 (en) * | 2021-12-03 | 2024-04-30 | Samsung Electronics Co., Ltd. | Systems and methods for automapping source code to machine code |
CN114090360B (zh) * | 2022-01-20 | 2022-04-22 | 苏州浪潮智能科技有限公司 | 一种服务器调试装置、方法及其介质和服务器调试器 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH04326844A (ja) * | 1991-04-26 | 1992-11-16 | Fujitsu Ltd | コマンド並列走行制御方式 |
JPH11184729A (ja) * | 1997-12-22 | 1999-07-09 | Hitachi Ltd | バグ情報管理表示方法及び装置 |
JP2001051871A (ja) * | 1999-08-09 | 2001-02-23 | Ricoh Co Ltd | リモートデバッグ装置 |
JP2004021751A (ja) * | 2002-06-19 | 2004-01-22 | Matsushita Electric Ind Co Ltd | デバッグ装置、デバッグプログラム、およびデバッグプログラム記録媒体 |
JP2010117810A (ja) * | 2008-11-12 | 2010-05-27 | Nippon Telegr & Teleph Corp <Ntt> | 競合調停装置及び競合調停プログラム |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH06103105A (ja) | 1992-09-18 | 1994-04-15 | Nec Software Ltd | タスク間共有ルーチン同時デバッグ処理装置 |
US6058393A (en) * | 1996-02-23 | 2000-05-02 | International Business Machines Corporation | Dynamic connection to a remote tool in a distributed processing system environment used for debugging |
US6324683B1 (en) * | 1996-02-23 | 2001-11-27 | International Business Machines Corporation | System, method and program for debugging external programs in client/server-based relational database management systems |
US6425101B1 (en) | 1998-10-30 | 2002-07-23 | Infineon Technologies North America Corp. | Programmable JTAG network architecture to support proprietary debug protocol |
US6684343B1 (en) * | 2000-04-29 | 2004-01-27 | Hewlett-Packard Development Company, Lp. | Managing operations of a computer system having a plurality of partitions |
DE60237433D1 (de) * | 2001-02-24 | 2010-10-07 | Ibm | Neuartiger massivparalleler supercomputer |
US7003698B2 (en) * | 2002-06-29 | 2006-02-21 | Intel Corporation | Method and apparatus for transport of debug events between computer system components |
US7339893B2 (en) * | 2003-03-18 | 2008-03-04 | Cisco Technology, Inc. | Pre-empting low-priority traffic with high-priority traffic on a dedicated link |
US7336676B2 (en) * | 2004-01-20 | 2008-02-26 | Mediatek Inc. | Multi-queue single-FIFO architecture for quality of service oriented systems |
JP2006139346A (ja) * | 2004-11-10 | 2006-06-01 | Renesas Technology Corp | デバッグ制御方法 |
US7760769B1 (en) * | 2005-11-15 | 2010-07-20 | Network Appliance, Inc. | Serial stream filtering |
US7606750B1 (en) * | 2006-03-30 | 2009-10-20 | Intuit Inc. | Method and system for displaying a spending comparison report |
CN101360067B (zh) * | 2007-07-30 | 2012-11-07 | 国际商业机器公司 | 基于消息收发系统的组联合调试系统、方法 |
US8074118B2 (en) | 2009-01-28 | 2011-12-06 | Dspace Digital Signal Processing And Control Engineering Gmbh | Method for influencing a control unit and manipulation unit |
US8897292B2 (en) * | 2012-12-31 | 2014-11-25 | Telefonaktiebolaget L M Ericsson (Publ) | Low pass filter for hierarchical pipelined distributed scheduling traffic manager |
-
2011
- 2011-12-07 US US13/992,539 patent/US9292395B2/en not_active Expired - Fee Related
- 2011-12-07 WO PCT/JP2011/078272 patent/WO2012077704A1/ja active Application Filing
- 2011-12-07 JP JP2012547887A patent/JPWO2012077704A1/ja active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH04326844A (ja) * | 1991-04-26 | 1992-11-16 | Fujitsu Ltd | コマンド並列走行制御方式 |
JPH11184729A (ja) * | 1997-12-22 | 1999-07-09 | Hitachi Ltd | バグ情報管理表示方法及び装置 |
JP2001051871A (ja) * | 1999-08-09 | 2001-02-23 | Ricoh Co Ltd | リモートデバッグ装置 |
JP2004021751A (ja) * | 2002-06-19 | 2004-01-22 | Matsushita Electric Ind Co Ltd | デバッグ装置、デバッグプログラム、およびデバッグプログラム記録媒体 |
JP2010117810A (ja) * | 2008-11-12 | 2010-05-27 | Nippon Telegr & Teleph Corp <Ntt> | 競合調停装置及び競合調停プログラム |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210263817A1 (en) * | 2020-11-09 | 2021-08-26 | Beijing Baidu Netcom Science And Technology Co., Ltd. | Method and apparatus for sending debugging instruction |
US11860749B2 (en) * | 2020-11-09 | 2024-01-02 | Beijing Baidu Netcom Science and Technology Co., Ltd | Method and apparatus for sending debugging instruction |
CN113068250A (zh) * | 2021-04-01 | 2021-07-02 | 广东电网有限责任公司清远供电局 | 一种时间同步装置、方法、设备及存储介质 |
CN113068250B (zh) * | 2021-04-01 | 2023-07-18 | 广东电网有限责任公司清远供电局 | 一种时间同步装置、方法、设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
US20130262930A1 (en) | 2013-10-03 |
US9292395B2 (en) | 2016-03-22 |
JPWO2012077704A1 (ja) | 2014-05-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2012077704A1 (ja) | デバッグスタブサーバ、デバッグ方法およびプログラム | |
US6718294B1 (en) | System and method for synchronized control of system simulators with multiple processor cores | |
JP6171386B2 (ja) | コントローラ、情報処理装置およびプログラム | |
US9984244B2 (en) | Controller, information processing apparatus, and recording medium | |
US8042086B2 (en) | Method and apparatus for verifying integrated circuit design using a constrained random test bench | |
US8522079B2 (en) | System and method for multi-core synchronous debugging of a multi-core platform | |
JP5996125B2 (ja) | システム構築支援装置 | |
JP6540473B2 (ja) | デバッグサポートシステム | |
JP6362821B2 (ja) | 制御装置、制御方法および命令セット | |
JP4600601B1 (ja) | デバッグ支援装置、デバッグ支援方法及びデバッグ支援プログラム | |
CN114548027A (zh) | 在验证系统中追踪信号的方法、电子设备及存储介质 | |
KR20110037140A (ko) | 임베디드 소프트웨어 가상 개발 환경을 제공하는 시스템 | |
JP7337503B2 (ja) | 試験装置 | |
JP2005084957A (ja) | 回路動作検証装置および方法 | |
CN110309056B (zh) | 一种用于软件输入输出功能测试的跨平台模拟系统 | |
JP2005250937A (ja) | マイクロコンピュータソフトウェアのプログラム検証装置 | |
KR20080013528A (ko) | 통합 프로토타이핑 방법 | |
JP4562439B2 (ja) | プログラム検証システムおよびプログラム検証システム制御用コンピュータプログラム | |
JP6278300B2 (ja) | リモート操作システム、無線通信ユニット、及びリモートデバッグシステム | |
JP6215033B2 (ja) | テスト制御装置、通信システム、テスト制御方法、及びテスト制御プログラム | |
CN116594830B (zh) | 硬件仿真工具、调试方法和存储介质 | |
CN110334015B (zh) | 一种白盒测试方法、装置、设备及介质 | |
JP2009258857A (ja) | デバッグ装置及びデバッグ方法 | |
CN118643771A (zh) | 调试逻辑系统设计的方法、电子设备及存储介质 | |
CN115793582A (zh) | 工业控制算法调试方法、系统、装置及电子设备 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11847090 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2012547887 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13992539 Country of ref document: US |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 11847090 Country of ref document: EP Kind code of ref document: A1 |