CN103823757A - P2P (peer-to-peer) platform batch debug method and device - Google Patents
P2P (peer-to-peer) platform batch debug method and device Download PDFInfo
- Publication number
- CN103823757A CN103823757A CN201410087437.3A CN201410087437A CN103823757A CN 103823757 A CN103823757 A CN 103823757A CN 201410087437 A CN201410087437 A CN 201410087437A CN 103823757 A CN103823757 A CN 103823757A
- Authority
- CN
- China
- Prior art keywords
- program
- node
- debugging
- module
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Abstract
The invention discloses a P2P (peer-to-peer) platform batch debug method and a P2P platform batch debug device. The P2P platform batch debug device comprises P2P end devices and a development end device which are connected with each other, wherein each P2P end device comprises a passive program synchronization module, a program starting module, a program recycling module and a debug information feedback module, and is deployed on each P2P node, the development end device comprises an active program synchronization module, a debug control module and a debug information receiving module and is deployed on a development node, and development programs can be deployed in batch. When developed programs are tested and debugged in a P2P environment, program files with the latest version are installed and deployed on a mass of nodes, the programs are started, and debug information is checked. The method of file automatic synchronizing, node batch control and debug information automatic display is adopted, so that programs developed by developers are automatically synchronized and deployed, debug information is fed back, and the work of manually synchronizing program files, starting programs and acquiring debug information aiming at the P2P nodes in the development process is omitted.
Description
Technical field
The present invention relates to a kind of remote testing device, relate in particular to a kind of P2P platform batch debugging method and device.
Background technology
Need the work of large amount of complex to complete towards the debugging of P2P application development.In the adjustment method of existing P2P program development, debugging each time all need to, after native compile, be sent to compiled program utilization copy or the method for FTP in each node of P2P environment.And manually boot each debugging machine program example, store Debugging message record into this locality.Finally, while checking Debugging message, need the long-range Debugging message of transferring to be recorded to developer's node, and check one by one.This kind of P2P adjustment method, in the time that P2P debugging node is more, has significantly increased the workload of the each P2P node of developer's remote debugging.
Now needing one badly can distribute debugged program by automatic batch, and automatic batch starts, and automatic batch transmission shows the P2P platform testing system of Debugging message, to improve developer's program debug efficiency.
Summary of the invention
The deficiency existing for solving prior art, the invention discloses a kind of P2P platform batch debugging method and device, realizes P2P platform application program batch debugging, makes developer can debug efficiently, easily P2P application program.
For achieving the above object, concrete scheme of the present invention is as follows:
P2P platform batch debugging method, comprises the following steps:
Be program file at exploitation end program compiler source code;
Synchronization program file is to each node;
Exploitation end utilizes debugging control module to send start-up routine order to each P2P node, and the program of each P2P node starts module working procedure example;
Each P2P end device Debugging message feedback module logging program Debugging message, and Debugging message Real-time Feedback is returned to exploitation end;
Exploitation end debugging control module sends termination routine order to each P2P node, the program recycling module termination routine example of each P2P node.
Described is program file at exploitation end program compiler source code, and developer's coding source code triggers batch debugging order after sending hold-over command, and batch debugging System build source code is program file.
Described synchronization program file is to each node, synchronous method is to utilize passive Program Synchronization module and active process synchronization module to detect P2P end and the similarities and differences of developing end program version, and the program file program version of exploitation end is sent to each P2P node as source file.
The comparison of the similarities and differences of described program version according to file name, file size, file amendment date and file Hash code as feature.
The described program file program version using exploitation end sends to each P2P node as source file, if loading error occurring in process of transmitting shows the node identification of makeing mistakes at exploitation end, and provides option to select to developer.
Described option comprises and ignoring, again transmits and finishes to be debugged.
Described exploitation end is monitored each P2P node running status and program file version, if each node running status is good, and program version is consistent with the program version of exploitation node, sends program startup command, each P2P node start-up routine example; If node operation is broken down, repair malfunctioning node; If there is inconsistent program version, re-synchronization program file is to each node.
Described each P2P node starts the Debugging message that the newly-built thread of example module returns for reception program example, and Debugging message is fed back to exploitation end, the source of each Debugging message of exploitation end Debugging message receiver module mark, and displaying debugging information in real time;
The program recycling module of described P2P node is also filed running log, and deletion can operating file, and replacement node resource is waited for the debugging of next program version.
P2P platform batch debugging device, comprise the P2P end device and exploitation end device that are connected, P2P end device comprises that passive Program Synchronization module, program start module, program recycling module and Debugging message feedback module, P2P end device is deployed on each P2P node, exploitation end device comprises active process synchronization module, debugging control module and Debugging message receiver module, and is deployed on exploitation node;
Passive Program Synchronization module and active process synchronization module, for detection of the similarities and differences of corresponding P2P end with exploitation end program version, and be transferred to each P2P node using the program file program version of exploitation end as source file;
Debugging control module, for sending start-up routine order to each P2P node, the program of each P2P node starts module working procedure example;
Debugging message feedback module, for logging program Debugging message, and returns Debugging message Real-time Feedback to exploitation end, the source of exploitation end Debugging message receiver module mark Debugging message, and displaying debugging information in real time;
Debugging control module, also for sending termination routine order to each P2P node, the program recycling module termination routine example of each P2P node, filing running log, deletion can operating file.
Described program starts module, is program file at exploitation end program compiler source code, and developer's coding source code triggers batch debugging order after sending hold-over command, and batch debugging System build source code is program file.
Described passive Program Synchronization module and active process synchronization module, synchronization program file is to each node, synchronous method is to utilize passive Program Synchronization module and active process synchronization module to detect P2P end and the similarities and differences of developing end program version, the program file program version of exploitation end is sent to each P2P node as source file, if loading error occurring in process of transmitting, show the node identification of makeing mistakes at exploitation end, and provide option to select to developer.
The comparison of the similarities and differences of described program version according to file name, file size, file amendment date and file Hash code as feature.
Described option comprises and ignoring, again transmits and finishes to be debugged.
Described debugging control module, the exploitation end each P2P node running status of monitoring and program file version, if each node running status is good, and program version is consistent with the program version of exploitation node, sends program startup command, each P2P node start-up routine example; If node operation is broken down, repair malfunctioning node; If there is inconsistent program version, re-synchronization program file is to each node.
Described Debugging message feedback module, each P2P node starts the Debugging message that the newly-built thread of example module returns for reception program example, and Debugging message is fed back to exploitation end, the source of each Debugging message of exploitation end Debugging message receiver module mark, and displaying debugging information in real time;
Described program recycling module is also filed running log, and deletion can operating file, and replacement node resource is waited for the debugging of next program version.
Beneficial effect of the present invention:
1. can dispose in batches development sequence.In P2P environment, latest edition program file need be installed, be disposed to test and the program of debugging exploitation on a large amount of nodes.This patent adopts autosynchronous method, and the program compilation that developer is developed is also transferred on each P2P node.Save the work of long-range upload file.
2. can batch start-up routine.Exploitation end sends startup command to each P2P node, each P2P node automatic Starting example.Save the each P2P node of Long-distance Control, and the work of start-up routine.
3. return in real time Debugging message.The debugging apparatus of each P2P node dynamically returns to the Debugging message of program example exploitation end, has saved the long-range work of transferring debugging log of developer.
Accompanying drawing explanation
Fig. 1 one-piece construction schematic diagram of the present invention;
Fig. 2 system flow schematic diagram of the present invention;
Embodiment:
Below in conjunction with accompanying drawing, the present invention is described in detail:
For making those skilled in the art can reappear model described in patent according to described content, by reference to the accompanying drawings the specific embodiment of the present invention is described in further detail.As shown in Figure 1-2:
P2P platform batch debugging device, comprise the P2P end device and exploitation end device that are connected, P2P end device comprises that passive Program Synchronization module, program start module, program recycling module and Debugging message feedback module, P2P end device is deployed on each P2P node, exploitation end device comprises active process synchronization module, debugging control module and Debugging message receiver module, and is deployed on exploitation node;
Passive Program Synchronization module and active process synchronization module, for detection of the similarities and differences of corresponding P2P end with exploitation end program version, and be transferred to each P2P node using the program file program version of exploitation end as source file;
Debugging control module is used for sending start-up routine order to each P2P node, and the program of each P2P node starts module working procedure example;
Debugging message feedback module is used for logging program Debugging message, and Debugging message Real-time Feedback is returned to exploitation end, and exploitation end Debugging message receiver module identifies the source of Debugging message, and displaying debugging information in real time;
Debugging control module is also for sending termination routine order to each P2P node, and the program recycling module termination routine example of each P2P node, files running log, and deletion can operating file.
P2P platform batch debugging method, concrete steps:
1) be program file at exploitation end program compiler source code.Developer's coding source code, triggers batch debugging order after sending hold-over command.Batch debugging device compiling source code is program file.
2) synchronization program file is to each node.Synchronous method is: first the Program Synchronization module of exploitation end and P2P node side device detects the similarities and differences of exploitation end and P2P end program file version, the comparison of the file similarities and differences according to file name, file size, file amendment date and file Hash code as feature.Secondly the program file of exploitation end is sent to each P2P node as source file.If loading error occurring, shows the node identification of makeing mistakes at exploitation end, and provides the option of ignoring, again transmit, finish debugging to select to developer.
3) exploitation end utilizes debugging control module to send start-up routine order to each P2P node, and the program of each P2P node starts module working procedure example.The exploitation end each P2P node running status of monitoring and program file version.If each node running status is good, and program version is consistent with the program version of exploitation node, sends program startup command, each P2P node start-up routine example; If node operation is broken down, repair malfunctioning node; If there is inconsistent program version, re-execute step 2).
4) each P2P end device Debugging message feedback module logging program Debugging message, and Debugging message Real-time Feedback is returned to exploitation end.Each P2P node starts the Debugging message that the newly-built thread of example module returns for reception program example, and Debugging message is fed back to exploitation end.The source of each Debugging message of exploitation end Debugging message receiver module mark, and displaying debugging information in real time.
5) exploitation end debugging control mould sends termination routine order to each P2P node, the program recycling module termination routine example of each P2P node.And file running log, and deletion can operating file, and replacement node resource is waited for the debugging of next program version.
Claims (10)
1.P2P platform batch debugging method, is characterized in that, comprises the following steps:
Be program file at exploitation end program compiler source code;
Synchronization program file is to each node;
Exploitation end utilizes debugging control module to send start-up routine order to each P2P node, and the program of each P2P node starts module working procedure example;
Each P2P end device Debugging message feedback module logging program Debugging message, and Debugging message Real-time Feedback is returned to exploitation end;
Exploitation end debugging control module sends termination routine order to each P2P node, the program recycling module termination routine example of each P2P node.
2. P2P platform batch debugging method as claimed in claim 1, it is characterized in that, described is program file at exploitation end program compiler source code, developer's coding source code, after sending hold-over command, trigger batch debugging order, batch debugging System build source code is program file.
3. P2P platform batch debugging method as claimed in claim 1, it is characterized in that, described synchronization program file is to each node, synchronous method is to utilize passive Program Synchronization module and active process synchronization module to detect P2P end and the similarities and differences of developing end program version, and the program file program version of exploitation end is sent to each P2P node as source file.
4. P2P platform batch debugging method as claimed in claim 1, it is characterized in that, the described program file program version using exploitation end sends to each P2P node as source file, if loading error occurring in process of transmitting, show the node identification of makeing mistakes at exploitation end, and provide option to select to developer.
5. P2P platform batch debugging method as claimed in claim 1, it is characterized in that, described exploitation end is monitored each P2P node running status and program file version, if each node running status is good, and program version is consistent with the program version of exploitation node, transmission program startup command, each P2P node start-up routine example; If node operation is broken down, repair malfunctioning node; If there is inconsistent program version, re-synchronization program file is to each node;
Described each P2P node starts the Debugging message that the newly-built thread of example module returns for reception program example, and Debugging message is fed back to exploitation end, the source of each Debugging message of exploitation end Debugging message receiver module mark, and displaying debugging information in real time.
6.P2P platform batch debugging device, it is characterized in that, comprise the P2P end device and exploitation end device that are connected, P2P end device comprises that passive Program Synchronization module, program start module, program recycling module and Debugging message feedback module, P2P end device is deployed on each P2P node, exploitation end device comprises active process synchronization module, debugging control module and Debugging message receiver module, and is deployed on exploitation node;
Passive Program Synchronization module and active process synchronization module, for detection of the similarities and differences of corresponding P2P end with exploitation end program version, and be transferred to each P2P node using the program file program version of exploitation end as source file;
Debugging control module, for sending start-up routine order to each P2P node, the program of each P2P node starts module working procedure example;
Debugging message feedback module, for logging program Debugging message, and returns Debugging message Real-time Feedback to exploitation end, the source of exploitation end Debugging message receiver module mark Debugging message, and displaying debugging information in real time;
Debugging control module, also for sending termination routine order to each P2P node, the program recycling module termination routine example of each P2P node, filing running log, deletion can operating file.
7. P2P platform batch debugging device as claimed in claim 6, it is characterized in that, described program starts module, be program file at exploitation end program compiler source code, developer's coding source code, after sending hold-over command, trigger batch debugging order, batch debugging System build source code is program file.
8. P2P platform batch debugging device as claimed in claim 6, it is characterized in that, described passive Program Synchronization module and active process synchronization module, synchronization program file is to each node, synchronous method is to utilize passive Program Synchronization module and active process synchronization module to detect P2P end and the similarities and differences of developing end program version, the program file program version of exploitation end is sent to each P2P node as source file, if loading error occurring in process of transmitting, show the node identification of makeing mistakes at exploitation end, and provide option to select to developer.
9. P2P platform batch debugging device as claimed in claim 6, it is characterized in that, described debugging control module, the exploitation end each P2P node running status of monitoring and program file version, if each node running status is good, and program version is consistent with the program version of exploitation node, send program startup command, each P2P node start-up routine example; If node operation is broken down, repair malfunctioning node; If there is inconsistent program version, re-synchronization program file is to each node.
10. P2P platform batch debugging device as claimed in claim 6, it is characterized in that, described Debugging message feedback module, each P2P node starts the Debugging message that the newly-built thread of example module returns for reception program example, and Debugging message is fed back to exploitation end, the source of each Debugging message of exploitation end Debugging message receiver module mark, and displaying debugging information in real time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410087437.3A CN103823757B (en) | 2014-03-11 | 2014-03-11 | P2P platform batch debugging method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410087437.3A CN103823757B (en) | 2014-03-11 | 2014-03-11 | P2P platform batch debugging method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103823757A true CN103823757A (en) | 2014-05-28 |
| CN103823757B CN103823757B (en) | 2016-05-04 |
Family
ID=50758838
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410087437.3A Active CN103823757B (en) | 2014-03-11 | 2014-03-11 | P2P platform batch debugging method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103823757B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112492052A (en) * | 2021-02-05 | 2021-03-12 | 智道网联科技(北京)有限公司 | Remote debugging method and device for intelligent networked vehicle data |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101118631A (en) * | 2006-07-31 | 2008-02-06 | 杨孝先 | Network system method for providing commodity exchange, and management method of commercial product data |
| US20090248381A1 (en) * | 2008-03-28 | 2009-10-01 | Microsoft Corporation | Predicate Checking for Distributed Systems |
| CN102638828A (en) * | 2011-02-12 | 2012-08-15 | 苏州达联信息科技有限公司 | Remote debugging method and device for railway track monitoring and sensing network |
| CN103414725A (en) * | 2013-08-21 | 2013-11-27 | 北京网秦天下科技有限公司 | Method and device used for detecting and filtering data message |
-
2014
- 2014-03-11 CN CN201410087437.3A patent/CN103823757B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101118631A (en) * | 2006-07-31 | 2008-02-06 | 杨孝先 | Network system method for providing commodity exchange, and management method of commercial product data |
| US20090248381A1 (en) * | 2008-03-28 | 2009-10-01 | Microsoft Corporation | Predicate Checking for Distributed Systems |
| CN102638828A (en) * | 2011-02-12 | 2012-08-15 | 苏州达联信息科技有限公司 | Remote debugging method and device for railway track monitoring and sensing network |
| CN103414725A (en) * | 2013-08-21 | 2013-11-27 | 北京网秦天下科技有限公司 | Method and device used for detecting and filtering data message |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112492052A (en) * | 2021-02-05 | 2021-03-12 | 智道网联科技(北京)有限公司 | Remote debugging method and device for intelligent networked vehicle data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103823757B (en) | 2016-05-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105302716B (en) | Test method, device under the development mode of interflow | |
| CN106104467B (en) | A kind of Automation arranging method and terminal | |
| CN109344065B (en) | Remote debugging method, debugging server and target machine | |
| US9355017B2 (en) | Automated error checking system for a software application and method therefor | |
| US9594549B2 (en) | Automated patch generation | |
| CN105338110A (en) | Remote debugging method, platform and server | |
| CN106557347B (en) | Software updating method and device | |
| CN103530150A (en) | Remote updating method for Linux operating system | |
| CN109558318B (en) | Code management method and code warehouse distributed system | |
| CN103077111A (en) | Method and system for locating continuous integration failed case | |
| CN104391705A (en) | Distributed automated testing framework applied to high availability cluster software | |
| CN105573794A (en) | Long-distance updating method and system for embedded system software | |
| CN109683905A (en) | A kind of system method for automatically releasing | |
| CN104125504A (en) | Deployment method, device and system based on continuous integration | |
| CN103685385A (en) | Method, system and device for file synchronization | |
| CN110008123A (en) | A kind of method of automatic deployment test software and corresponding device | |
| CN104468260A (en) | Recognition method, device and system for mobile terminal device | |
| US10606730B2 (en) | Networked digital data processor log file viewer | |
| CN111651352B (en) | Warehouse code merging method and device | |
| CN111611157B (en) | GMS continuous integration construction automatic test method and system | |
| CN103678007A (en) | Method and system for deploying software in batches | |
| CN103823757B (en) | P2P platform batch debugging method and device | |
| CN105468507A (en) | Branch fulfillment detection method and apparatus | |
| CN105446873A (en) | Automatic test method and system of APK (AndroidPackage) software on the basis of android platform | |
| CN107766247B (en) | Method and device for testing Bootloader and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |